Guides
How to work with concurrency limits
Jobs queue and it is not clear which limit is binding.
4 min read
Jobs queue and it is not clear which limit is binding.
Why it happens
Limits exist at plan level, runner group level and workflow level, and they interact.
How to fix it
- Check the workflow's concurrency block first — the most common cause
- Then check runner group caps, then plan limits
- Use a provider with unlimited concurrency if you are structurally capped
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.