Queue and capacity
Your workspace runs a limited number of agents at the same time. Each running agent takes one slot. When every slot is busy, or a task is waiting for something else, the task joins the queue and starts by itself as soon as it can.
Why a task waits
| Reason | Starts when |
|---|---|
| All of your workspace's slots are busy | Another of your tasks finishes or is cancelled. |
| The platform is at capacity | Room frees up on the platform. |
| Its blocking issues are not done | The issues that block it in Linear are finished. |
| It is waiting for CI checks | The pull request's checks finish. A task blocked by failing checks waits up to 7 days for a re-run to pass. |
| The AI provider is unavailable | The provider responds again. |
| It is on hold | An admin releases it. |
How you see it
- In Linear, the issue gets the
queuedlabel and a comment such as "⏳ Queued — … Position 2. Resumes automatically when …". When it starts, the agent comments "▶️ Resumed after …". - On the Workflow board, the To do list shows how many tasks are waiting for an agent and their order: Next, 2nd, 3rd and so on.
If you send the agent a message while the task is still queued, it replies that the message was not delivered yet. Send it again once the task has started.
How waiting tasks start
ThriveOnDev checks the queue about once a minute and starts the next task that can run. If a task fails to start three times, the agent comments "⚠️ Could not start …" and explains why.
Cancel a waiting task
Any member can cancel a task in the To do list: choose Cancel task and confirm. To stop a task that is already running, press stop on the agent session in Linear.
How many slots you have
The number of slots is set per workspace. Shared slots are why one long task can delay others: splitting work into smaller issues keeps the queue moving. If your team regularly waits for slots, contact ThriveOnDev at info@thriveondev.com.