Skip to main content

Tasks

Why is my task stuck in Queued?​

A task needs a free worktree slot of its project to start. While every slot is held by another task or a person, it waits as Queued and starts as soon as one frees up. If it never starts, check that the project has a node that's online and enabled, in All or in one of its node groups, and that your organization has a model account that can run on that node. To run more tasks at once, add another node.

Read more in How worktrees work and How nodes work.

What happens when a task fails?​

A failed run uses one attempt, and Jaah queues the task again by itself. Only when every attempt has failed does the task stop as Failed. Nothing retries a Failed task: it waits for you. Read its Outcome and Timeline on its Details tab, fix what it needed, then select Start to try again, or Reset to start over from a clean draft.

See How tasks work and Read a task's result.

What's the difference between Stop and Reset?​

Stop pauses a task and keeps everything: its worktree, its work and its history. Start carries on from where it stopped. Reset returns the task to a clean Draft: the runner is stopped, its questions, report and outcome are no longer shown, and work it hadn't delivered is discarded. The description and attachments stay. Use Stop to pause, and Reset to try again from scratch.

The steps are in Stop, restart or reset a task.

Should I start a task or an epic?​

Choose Task when one runner can deliver the work as a single merged change. Choose Epic when it's too big or too unclear for that: a new area of your product, a change that touches many parts, or a goal you can describe but not yet break down. Jaah splits an epic into subtasks that run in stages. An epic costs more, because several runners work on it.

See How epics and features work and Start an epic.

Why is a subtask of my epic Waiting?​

An epic's stages run in order, and a subtask starts only when the stages before it are done: Design waits for Analyze, Plan waits for both, every Coder subtask waits for Plan, and Finish waits for every Coder. Hover the Waiting badge to see which stage it waits for. If that stage Failed, fix or restart it and the epic carries on.

See How epics and features work and Steer an epic's subtasks.

Why did my support ticket turn In progress?​

Someone is working on it. A ticket turns In progress when the support team starts on it, or when a task linked to it starts running; the ticket's Details tab lists those Linked tasks with their state. No email is sent for this change: you get one when the team replies, or when the ticket is marked Solved or Closed.

See Support and How tasks work.

Can I run a whole epic again from scratch?​

Yes. Open the epic, select ⋯ at the top right, then Reset, and confirm with Reset. The epic and every subtask go back to clean drafts: their questions, answers, reports and outcomes are no longer shown, and any live runner is stopped. Descriptions and attachments stay, and changes its subtasks already merged stay merged. Change the epic's description to say what went wrong, then select ⋯ and Start: it runs again from Analyze. To redo one subtask only, reset that subtask instead.

See Run an epic again from the start and Steer an epic's subtasks.

Can I check each stage of an epic before the next one starts?​

Yes: set its Throttle to Manual. On New Task, select Epic, then Advanced, pick Manual in Throttle and select Go. Each subtask then waits as Held. When one is done, read its Artifacts tab; then, on the epic's Subtasks tab, open the next Held subtask and select Start in its ⋯ menu. To let the epic run on its own again, set Throttle to No under Advanced on its Task tab and save.

See Run an epic one stage at a time and How epics and features work.

Can I limit how many subtasks of an epic run at once?​

Yes. Set the epic's Throttle, under Advanced, to a number: at most that many of its subtasks run together, and the rest wait their turn. Set it when you start the epic, or later on its Task tab and select Save. Raising it lets waiting subtasks start; lowering it stops the most recently started ones, which resume where they stopped when a place frees. No removes the limit, and Manual holds every subtask until you start it.

See Limit how many subtasks run at once and How epics and features work.

Can a task wait until another task is done?​

Yes. Open the task that should wait, select Advanced on its Task tab, and in Add a prerequisite type the other task's number, link or part of its title. Pick it, then select Save. Once you start the task, it shows Waiting on the board until every prerequisite is done and its change has merged, then runs. Its Details tab names each task it waits for under ⛔ Blocked by. Jaah refuses a prerequisite that would make two tasks wait on each other.

See Make a task wait for another task and How tasks work.

Where did my finished tasks go?​

They are in Done, folded away at first. Under Tasks on the board, select ▸ beside Done to open it; the board remembers your choice. The tasks a release shipped fold under that release, such as v1.8.2 · Production: select ▸ on it to see them. If Done is missing, Focus (the pulse icon) may be on, which hides finished tasks: select it again. Under Pipeline, a finished task stays in its stage. One that changed no code sits in the folded ✓ Done row at the end of the first stage, and one filed by a schedule, a trigger or an agent in the folded Automatic row.

See Task board and Find finished tasks that changed no code.

Can I change a task while it's running?​

Yes, but the run in progress keeps the old version. Select ⋯, then Edit, change the description or settings and select Save: the change is kept for the task's next run. While a task runs, is queued or waits on a question, there is no Go. To run it with the change now, stop it and start it again. To steer the run in progress instead, select Open web console beside its state and send the agent a message; it reads it on its next turn.

See Edit a task and Chat with a running task.