Flow Level Concurrency Throttling #4429
Unanswered
mhmcdonald
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, limiting concurrency at a Flow level can be done using labels. If you want to have flow level throttling isolated to a specific flow rather than a group of flows, you end up having a label per flow. In this case, it seems to me that you should be able to throttle based on flow id or flow name + project.
My specific use case: I have a single flow where I want to limit concurrency to one flow run at a time for business logic reasons. At my company, we use labels to tag flows by team (business-intelligence, data-engineering, machine learning, etc) and by environment (uat, prod) for routing to the appropriate agent.
While I can make labels work for my use case, I would end up having a label per flow (for those flows where I want to limit concurrency).
We also decouple flow deployment from agent deployment. So every time I want to deploy a new label for throttling flow concurrency, I have to redeploy my agents.
My idea: this UI could allow you to search by flow name and project to enable concurrency-limiting
Beta Was this translation helpful? Give feedback.
All reactions