We have been exploring using events with Argo Workflows. So far we have events triggering correctly, but the GUI features in this video aren't working consistently: https://docs.metaflow.org/production/event-triggering/inspect-events#events-in-the-metaflow-ui. We do see the trigger on the runs list, but only if the runs list is open before the run is triggered. If I refresh the page or load the runs list after the run triggers, I don't see the trigger information. I also don't see any of the trigger information on the page for the specific run. Does anyone have any idea what might be wrong? We are using Metaflow 2.9.15, Service 2.4.3, and UI 1.3.6.

investigating...

Hi @quiet-afternoon-68940 - we ran into a similar issue with another deployment

do I need to have an event triggered runs visible? or just any UI page?

any run page would be a good start. The bug that we found was independent of triggers

oh yes, I see lots of failures

Look for the first request to

metadata

(one without the

_page=2

parameter)

okay, found that

Can you share a screenshot of that field opened?

some of that might be confidential; here's a redacted JSON blob:

{
  "self": "<http://metaflow-service.dev>.<domain>/api/flows/<FlowName>/runs/35255/metadata?step_name=start",
  "first": "<http://metaflow-service.dev>.<domain>/api/flows/<FlowName>/runs/35255/metadata?step_name=start&_page=1",
  "prev": "<http://metaflow-service.dev>.<domain>/api/flows/<FlowName>/runs/35255/metadata?step_name=start&_page=1",
  "next": "<http://metaflow-service.dev>.<domain>/api/flows/<FlowName>/runs/35255/metadata?step_name=start&_page=2",
  "last": null
}

Is

<http://metaflow-service.dev>.<domain>/api/flows/<FlowName>/runs/35255/metadata?step_name=start

the same as the request URL for that request?

it is the same as the request URL, and I do get a result when I paste into my browser

do you get an error when you add

&_page=2

? And is that URL the same as the ones that you showed with errors in the earlier screenshot?

yes and yes