Hi all, I have a deployment with a concurrency limit, and I’m using a Kubernetes work pool. When I create more flow runs than the concurrency limit allows, I expect the extra flow runs to be enqueued and executed as slots become available. However, even after the other runs are completed, the additional ones remain stuck in the "Awaiting Concurrency Slot" state. Any ideas why this might be happening? Thanks.

Hi Eren! I believe what you're seeing may be related to this issue in GitHub. Our team is taking a look.

Thanks for letting me know Bianca!