A task is stuck or failed
A task's pill on the board names its state; hover it for the reason. What each state means is in How tasks work.
It stays Queued
Symptom: the pill reads Queued and the task never starts.
Cause: a task needs a free worktree slot of its project on a node that is online, enabled, open to the project (in All, or in one of its node groups), and has an AI account signed in. Until one is free, it waits.
Fix:
- If other tasks of the project are running, wait: it starts as soon as one finishes.
- If nothing is running, check the project's nodes: in the sidebar select Directory, then Machines, and read each node's dot and Enabled; open the node and read Accounts on its Overview tab.
- Fix the node as in The node is online but runs nothing.
- If the project's node groups hold no enabled node, add a node to one of them, or change the project's Node groups, in the project's Settings tab, section Nodes.
- To run more tasks at once, add another node. See Give a project more slots.
It says Waiting
Symptom: the pill reads Waiting.
Cause: the pill or its hover names what it waits for:
- Organization runner limit, such as Waiting · Organization runner limit (1/1): your plan's agents are all busy.
- Waiting for your node: it starts once your node is online.
- A prerequisite: a task it depends on isn't done yet.
Fix: for the runner limit, see Tasks wait on the runner limit. For a node, bring it online (A node is offline). For a prerequisite, open the task it depends on and get it done.
It says Asking
Symptom: the pill reads Asking, and the task's board section is Stopped.
Cause: the runner has a question only you can answer, and waits for you.
Fix:
- Select the task. It opens on the Q&A tab, one page per open question.
- Pick an option for each, or type your answer in its box. Add a Note if the options miss something.
- On the last question, picking or Send sends every answer together. The pill turns Delivering, then Running.
The steps are in Answer a question.
It says Paused
Symptom: the pill reads Paused.
Cause: someone selected Stop, or Jaah paused it because your Jaah balance ran out. The task's banner names which, such as Paused — balance below floor.
Fix: select Start to carry on from where it stopped. A task Jaah paused for the balance starts by itself once the balance is back: see A billing problem or a plan limit.
It ended as Failed
Symptom: the pill reads Failed.
Cause: every attempt failed. A failed run uses one attempt and is queued again by itself; only after the last attempt does the task stop as Failed. Common reasons: the AI account hit its usage limit or its sign-in was refused, the node went away, or the task asked for something the project can't give, such as a missing credential.
Fix:
- Hover the pill, or open the task, and read the reason in its banner.
- On its Details tab, read Summary and Timeline for what the runner did and where it stopped.
- Fix the cause: sign the AI account in again (Sign a model account in again), bring the node back, or add the missing credential under Directory > Secrets and attach it to the project (Attach a credential to a project).
- If the description was unclear, open the task's ⋯ menu on the board, select Edit and say what was missing.
- Select Start to try again with the work so far, or open ⋯ and select Reset to start over from a clean Draft.
See Stop, restart or reset a task and Read a task's result.
It's Done but nothing merged
Symptom: the task is Done, but its pull request is still open.
Cause: the project's merge lane merges it after the task settles.
Fix: see A pull request won't merge.
Related
- How tasks work — the lifecycle and attempts.
- Write a good task — avoid tasks that fail for lack of detail.
- FAQ: tasks — short answers.