@Marvin When i go to edit deployment, the concurrency limit there is strict to that deployment rerunning over itself is that correct?

Yes, your understanding is correct. The concurrency limit set on a deployment in Prefect is primarily to control the degree to which that specific deployment can run concurrently. It prevents the deployment from rerunning over itself or running multiple instances if the limit is set to a lower value. For Prefect 2.x, concurrency limits can be managed via the Prefect UI and CLI, and are generally applied as a global limit which then can influence deployment behaviors. More information for Prefect 2.x is available here: Prefect 2.x Concurrency Limits Guide. In Prefect 3.x, concurrency limits are set at a deployment level and can also be configured via work pools or work queues. You can manage these using the Prefect CLI, API, or UI. More detailed guidance can be found in the Prefect 3.x documentation: Prefect 3.x Concurrency Limits. And remember, setting a concurrency limit too low might make your flow runs a bit grumpy from waiting—sort of like keeping them in a queue for the next rollercoaster ride. 🎢