# All builds are stuck in queue

**URL:** <https://discuss.circleci.com/t/all-builds-are-stuck-in-queue/43994>\
**Category:** Bug Reports\
**Created:** [May 10, 2022, 3:23pm UTC](https://discuss.circleci.com/t/all-builds-are-stuck-in-queue/43994 "2022-05-10T15:23:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JekRock](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jekrock/32/30123_2.png) [@JekRock](https://discuss.circleci.com/u/JekRock)\
**Post date:** [May 10, 2022, 3:23pm UTC](https://discuss.circleci.com/t/all-builds-are-stuck-in-queue/43994/1 "2022-05-10T15:23:41Z")

</div>

All builds on multiple repositories in our organization have been stuck for more than 3 hours. Restarting the builds doesn’t solve the issue.  
The runners are CircleCI runners, not self-hosted.

CircleCI status page says that all systems are operational.  
How can this issue be resolved?

---

<div class="post-metadata">

**Author:** ![yannCI](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/yannci/32/24866_2.png) [@yannCI](https://discuss.circleci.com/u/yannCI)\
**Post date:** [May 26, 2022, 4:55pm UTC](https://discuss.circleci.com/t/all-builds-are-stuck-in-queue/43994/2 "2022-05-26T16:55:00Z")

</div>

👋 Hi @JekRock,

The situation you’re describing suggests that, at the time, your organization had reached the plan’s concurrency limit.

Note that if a job is configured to execute parallel runs, the job won’t start until at least as many containers as the `parallelism` value are available.

Please see [this blog post](https://circleci.com/blog/config-best-practices-concurrency-parallelism/) from our Technical Community Manager to learn more about concurrency and parallelism in CircleCI.