Abort, Pause, Resume, Delete
Open an attempt's actions in the Dashboard, then choose the control based on what you want to happen next. How Dispatch Decides explains how work is picked. This page explains the four controls you can use after work has started.
Keep an Issue Out of Zozo Entirely
Apply not-for-agent in GitHub when an Issue is human-owned work that Zozo must behave as though it doesn't exist. Zozo won't pick or promote it, show it on Needs Attention, or include it in a Project panel. Record the reason in the Issue body because the label states only the exclusion.
Use Label Reference to choose the Control Label that matches the reason. In particular, needs-info means a dispatch attempt has ended and needs human review. It isn't a general waiting-for-an-answer label.
Choose the Outcome You Want
| Control | Use it when | What changes |
|---|---|---|
| Pause | You want work on the Issue to stop for now, but you plan to continue the same attempt. | The active Run is interrupted and the attempt shows as paused. Its history and work are kept, and the Issue remains in progress until you choose Resume or Delete. |
| Resume | You want to continue a paused attempt. Resume is also available when an attempt shows as stuck because it no longer has an active Run. | Zozo continues the existing Thread and keeps its previous context and work. The new Run starts when capacity is available. |
| Abort | You want to stop the active Run and make the unresolved Issue available for a fresh attempt. | The Run ends as aborted, but the Thread and its history remain in the Dashboard. The Issue returns to ready-for-agent unless it has already been closed or merged. |
| Delete | You want to abandon an idle or paused attempt and remove its history. | Zozo deletes the Thread and all of its Runs and recorded history. The unresolved Issue returns to ready-for-agent so the Dispatcher can start a fresh attempt. |
The Dashboard only shows actions that are valid for the attempt's current state. An active Run offers Abort and Pause. A paused attempt offers Resume and Delete. An idle attempt offers Delete, with Resume added when the attempt is stuck.
Pause Now and Resume Later
Choose Pause when you don't want the current attempt to keep running, but you do want to return to it. Pausing interrupts an active Run and prevents Zozo from starting another Run on that Thread. It keeps the attempt's work and leaves the Issue's agent-in-progress label in place.
Only Resume restarts a paused attempt. When you choose it, Zozo continues the same Thread instead of creating a fresh attempt. If every work slot is occupied, the request waits in the queue and the attempt continues to show as paused until a slot is available. The resumed Thread keeps its selected Credential, model, and effort; tuning edits apply to new Threads.
Once work starts, Zozo makes 2 attempts by default to recover the attempt. The result determines what you see next:
- When the resumed work succeeds, Zozo removes
agent-in-progress. If its Pull Request needs attention before it can merge, Zozo addslanding-blocked. - When both recovery attempts fail, Zozo removes
agent-in-progress, addsneeds-info, and leaves the Issue for you to review. - When the Runtime is unavailable, Zozo keeps the Issue in progress so it can try again after the Runtime recovers.
Abort a Run or Delete an Attempt
Choose Abort while a Run is active. Zozo stops that execution, keeps the Thread's history for reference, and returns an unresolved Issue to ready-for-agent. You can review the stopped attempt in the Dashboard while the Dispatcher is free to start a fresh one.
Choose Delete when no Run is active and you no longer need the attempt or its history. Deleting removes the whole Thread, including every Run and recorded history it contains. For an unresolved Issue, it also replaces agent-in-progress with ready-for-agent. A closed or merged Issue isn't made ready again.
Protect Unshipped Work
An Unshipped Attempt is marked unshipped because it has commits that haven't reached a Pull Request. The Dashboard warns you before an action would discard the only copy of those commits. The Dashboard doesn't provide access to the code in that attempt, so the warning is your choice between preserving the attempt and discarding its work.
Continue with Delete only when you're willing to discard that work. If an Abort stops the Run but Zozo then discovers unshipped commits, it keeps the Issue in progress and preserves the attempt. You can leave the attempt in place, or use the Delete confirmation to discard it and return the unresolved Issue to ready-for-agent.
Related
- How Dispatch Decides: how an Issue is selected and who receives the next work slot.
- Label Reference: what the labels shown in the Dashboard mean.
- Work Model: why Resume may wait for capacity.