@ancient-wolf-19325 Can a workflow have a mutex to ensure only one is running?

Flyte currently does not support workflow-level mutex natively to ensure only one instance of a workflow is running at a time. However, there are ongoing discussions and feature requests to implement such functionality. According to Flyte GitHub issue #5125, there are proposals to introduce workflow-level throttling, which would limit the number of concurrent executions of the same workflow. This would involve extending the

ExecutionManager

to track active executions and enforce concurrency limits. Similarly, Flyte GitHub issue #267 also discusses the need for preventing concurrent executions of workflows. Would you like more details on potential workarounds or the current state of these feature requests? Sources: - Flyte GitHub issue #5125 - Flyte GitHub issue #267 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.