Hey, I would like to set a concurrency limit that all deployments I make can only ever have one instance of a flow running at a given time. I've seen that I'm able I'm able to set concurrency limits based on a tag. My thoughts are I could give each of the deployments a unique tag, and alongside that set a concurrency limit of 1 for the tag I just created but I'm curious if you can see a more generic way of imposing this?

Tag sounds like the right choice here

this is something we'll be improving in the near future (a more general concurrency interface), but tag-based concurrency is for tasks you'd set flow run concurrency on the work pool and/or work queue level

Gotcha, good to hear it's on the roadmap. So in the case of work queue it would likely be setting the concurrency limit on the work queue (avoiding having to set up multiple agents, one for each work pool) and then assign each deployment with a unique work queue