Check on a task that won't start in its slot
A started task takes a slot on a node, and the node launches its run there. The run usually reports back within a minute or two. When it doesn't, the task keeps its slot but does no work. The task's Runner field shows how long it has waited, and its console shows what the run is stuck on.
Who can do this: anyone who can see the task can read Runner. The silent-launch warning and the Open web console button need the permission to view worktrees, and the button shows only when you can act on the task. The Sessions link needs the permission to view sessions. Resetting and starting the task need edit access to its project.
- Open the task. Hover the state icon at the top of its page:
- Queued. Holds slot … followed by a slot number and a node: a node holds a slot for the task and is launching its run.
- Starting: the run was launched and the task waits for it to report.
- Select the Details tab and find Runner on Summary. It reads starting… with how long it has waited, then on, the node and the slot, such as · slot 1.
- Give it five minutes. After that, Runner reads no session in place of starting…, or a warning shows under it: Launched … ago, still silent — open the console to see what it is waiting on.
- Select the Open web console button beside the state at the top of the page. On a phone, select ⋯, then Console. The console opens on the task's slot.
- Read what the run shows. A run often waits on a prompt or stops at an error, and the last lines say which. Fix the cause where it lives: a model account that needs signing in again, a project setting, or the task's own description.
- To see earlier tries, select Sessions in the Runner field. Audit › Sessions opens on this task's runs. A try that ended before it reported is listed under Attempts with no session, with its Cause and Node.
- Check that the node from Runner is online: in the sidebar, select Directory, then Machines; the Nodes tab opens. If it is offline, follow Move a task off an offline node instead.
- Start the task over. Open the ⋯ menu at the top of the task's page, select Reset, then select Reset in the dialog. The task goes back to Draft and lets its slot go.
- Open the ⋯ menu again and select Start. The task takes a slot again and Runner shows the new run.
If the same task stalls again on the same node, read the node's status before you start it a third time; see Read a node's status.
Related
- How worktrees work: who holds a slot, and for how long.
- Chat with a running task: what the console shows once a run is going.
- Find out why a session ended: end reasons and pane logs for runs that did start.
- See what ran in a slot: every run one slot hosted.