If a local agent is running connected to a remote prefect server, and prefect ui shows the agent is indeed active, what could be the reason for a late flow when using "quick run"?
p
Pedro Machado
12/23/2020, 2:38 PM
In my experience, it's usually due to label mismatch between the flow/flow run and the agent.
➕ 1
m
Mariia Kerimova
12/23/2020, 3:02 PM
I've seen late runs often occurring due to label mismatch too, but let us know if you are facing a different issue.
a
Amanda Wee
12/24/2020, 12:58 AM
Ah, thank you. However, I have not set any labels at all. Should I set a consistent label for the flows and agent?
m
Mariia Kerimova
12/24/2020, 1:56 AM
You can do that, but make sure that labels for agent are superset of labels on the flow. You can see an example here.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.