Knob
Concurrency limit
You might say: WIP limit, parallelism cap, concurrency group
A bound on how many runs or jobs may be active together for one key, repository, branch, or resource.
- What it does
- Prevents conflicting runs and keeps the runner pool and review queue within capacity.
- Ask
- What is the key, how many runs may be active, and should a new run wait, replace, or cancel an older one?
- Typical
- One active run per group, a small fixed worker pool, or a larger queue with explicit cancellation rules.
- Trouble
- Parallel runs edit the same target, stale runs consume capacity, or the cap hides a slow downstream gate.
What to look for
- A concurrency group name
- A counter or queue badge
- A cancel-in-progress or pending policy
Pattern
Connections
- See also: Work claim
- See also: Throttle
Sources
- GitHub, Control the concurrency of workflows and jobs, Using concurrency in different scenarios
You can use `jobs.<job_id>.concurrency` to ensure that only a single job or workflow using the same concurrency group will run at a time.
- Dan Radigan, Working with WIP limits for kanban, What are WIP limits?
In agile development, work in progress (WIP) limits set the maximum amount of work that can exist in each status of a workflow.
Use it on your project
teardown-apply: hold "Concurrency limit" (concurrency-limit) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal