Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> is managing concurrency at the deployment level using  `concurrency_limit`  and `collision_strategy`  available in Prefect v2.x or exclusive to Prefect v3.x?

:white_check_mark: thought for 72.2 seconds

Short answer: Deployment-level `concurrency_limit` and `collision_strategy` are Prefect 3.x features. They are not available in Prefect 2.x.

In Prefect 2.x, concurrency was managed via global concurrency limits (typically applied to task tags) rather than per-deployment settings. See:
- Prefect 2.x global concurrency limits: <https://docs-2.prefect.io/latest/guides/global-concurrency-limits/|Docs (2.x)>

In Prefect 3.x, you can manage concurrency more granularly, including at the deployment level, and also use the CLI to manage limits:
- Prefect 3.x global concurrency limits: <https://docs-3.prefect.io/v3/how-to-guides/workflows/global-concurrency-limits|Docs (3.x)>
- Prefect 3.x CLI for concurrency limits: <https://docs-3.prefect.io/v3/api-ref/cli/concurrency-limit|CLI reference (3.x)>

If you’re on 2.x and want similar behavior, the closest approach is to use global concurrency limits on tags and/or control concurrency within a single flow run via the task runner settings. If you’d like, I can show a quick example for 3.x deployments using these fields.