There’s a lot of flexibility in terms of how you could design the process here.
- You could split this long-running process into smaller parts e.g. leveraging subflows
- You could leverage the orchestrator pattern to coordinate codependent deployments How to create a flow run from deployment (orchestrator pattern)?
- You can set a concurrency limit of 1 per queue and run multiple queues and agent processes
- You can switch to some more reliable execution layer e.g. leverage the power of Kubernetes for better resource utilization
It’s already possible to have multiple agents polling from the same work queue and setting concurrency limits set on this work queue. It might be worth cross-checking the flow design to ensure not everything runs as part of one large flow to better separate that load