@Marvin using prefect 2 with prefect cloud. In my prod workpool, i had concurrency set up at 20. But even when there were less than 20 flow runs running, there were a bunch being scheduled and stalled. I raised it to 25 for now, but I want to see if there are any remaining artifacts that might be causing this behavior

It seems like you're experiencing issues with flow runs being scheduled and stalled despite having a concurrency limit set. Here are some insights that might help: 1. Concurrency Limits and Work Queues: Each work pool in Prefect can have multiple work queues, each with its own concurrency limits. However, these queues are still subject to the global work pool concurrency limit. You might want to ensure that no individual work queue has its own concurrency limit set lower than expected, as it could be affecting the overall scheduling behavior. Work Pools and Queues Documentation 2. Flow Suspension: If flows are being paused or suspended, they might appear stalled. Ensure that no flows are being unintentionally paused. Flow Suspension Documentation 3. No Known GitHub Issues: There are no open GitHub issues directly related to concurrency causing scheduled flows to stall. It may be worthwhile to review your work queue configurations and ensure they are aligned with your expected concurrency behavior. If the problem persists, consider reaching out to Prefect support or checking for any updates or patches that might address this issue.