When using
.serve
on a flow to create a deployment on your local machine, the documents don't specify a default concurrency limit for flows. However, Prefect allows you to define custom
concurrency limits at various levels, including task and flow concurrency, using context managers such as
with concurrency(...):
.
For local deployments, one might specify concurrency limits while defining task execution limits, but the documents retrieved in the search do not explicitly describe flow concurrency limits for local deployments initiated with
.serve
.
For more details and to explore using concurrency limits for tasks in your flows, you can reference the documentation on
global concurrency limits.
If you're looking for concurrency behavior specifically tied to local deployments with
.serve
, you may need to test empirically by serving multiple deployments and observing their behavior, or consult further documentation and community discussions for anecdotal evidence.