@Marvin Is there a "max queue depth" of flows waiting to run in a workpool with concurrency limits?

In Prefect 2.x, each work pool has a "default" queue that all work will be sent to by default, but you can add additional queues to a work pool. Work queues enable control over work delivery through fine-grained priority and concurrency. Each work queue has its own priority, indicated by a unique positive integer, with lower numbers having greater priority in the allocation of work. New queues can be added without changing the rank of the higher-priority queues. Additionally, work queues can have their own concurrency limits. Regarding the "max queue depth" or the handling of flow run concurrency limits, they are set on work pools. The documentation does not explicitly mention a maximum queue depth limit. The concurrency limits can be customized with the open-source Prefect server and Prefect Cloud. These limits will control how many flow runs can execute concurrently within a work pool or a queue, which suggests that as long as there is availability within the concurrency limits, Prefect 2.x will manage and queue the flow runs accordingly. For more specific details on max queue depth, it might be necessary to look into the Prefect 2.x source code or the official documentation, neither of which are directly stated in the excerpts provided. You can find additional information about work pools and queues in the Prefect documentation here and information about concurrency limits in migration guides.