When work is underway and you no longer want it to finish — the wrong task started, the approach is off, priorities changed — you can stop it. DIJJI.ai gives you two ways to stop, and they’re not the same thing. This page covers both and when to reach for each — plus how to pause a run instead of stopping it, and how to clear tasks you no longer need. For the states a run moves through, see Run states.
Cancel the run, or cancel the task
A task is the piece of work; a run is one attempt at delivering it. A task can have several runs over its life. That’s why there are two controls:
- Cancel Run ends the current attempt. The task stays open, and you can start a fresh run on it later.
- Cancel Task ends all work on the task. The current run stops and no future runs will start.
Reach for Cancel Run when this attempt has gone wrong but the task is still worth doing. Reach for Cancel Task when you don’t want the work done at all.
Cancel the current run
Open the run detail page for the run you want to stop. While the run is in the Running state, a Cancel Run button sits in the action bar near the top of the page.
Select it. A confirmation appears:
Are you sure you want to cancel this run? The process will be stopped and cannot be resumed.
Choose Cancel Run to confirm, or dismiss the dialog to leave the run alone. Cancelling is immediate and final — the run can’t be resumed afterwards.
Once confirmed, the run leaves Running and ends in the Cancelled state. The run detail page stays as a record of how far the attempt got.
The Cancel Run button is for a run that’s actively Running. If a run is instead paused waiting on you — for a gate, an answer, a plan approval, or payment — end it through the pause itself: reject the plan, or cancel the whole task as described below.
Pause instead of stopping
Cancelling is final. If you only want to stop work for now — to take a closer look, or come back to it later — pause the run instead.
While a run is Developing, a Pause button appears in the action bar on the run detail page. Select it and the run finishes the step it’s on (showing Pausing… in the meantime), then settles into the Paused state with your place kept. Select Resume — on either the run or the task detail page — to continue from the step after the pause; nothing already done is repeated.
Pausing isn’t the same as cancelling: the attempt isn’t called off, and the project stays busy with the paused run rather than freeing up. To release the project, cancel the task. For the full walk-through, see Pause and resume a run; for how Paused fits among the other states, see Run states.
Cancel the whole task
Open the task detail page. In the action bar, next to the Run / Re-run button, is a Cancel button.
Select it. A confirmation appears:
The task will be cancelled. The current run will finish its current step (e.g. develop, test) and then stop gracefully — work in progress is preserved.
Choose Cancel Task to confirm. Unlike cancelling a run, this is a graceful stop: the run finishes whatever step it’s on right now before stopping, so partial work isn’t thrown away mid-step. After that, no further runs start on the task.
What cancelling does and doesn’t touch
- Completed work is kept. A cancelled run’s record — the steps it took, the stages it reached, what it cost — stays on the run detail page.
- Spend already incurred isn’t refunded. You’re charged for the work that ran before you cancelled; cancelling just stops anything more from running.
- An open pull request stays open. If the run already opened a pull request on GitHub, cancelling doesn’t close it. Close or keep that pull request yourself on GitHub.
- The project frees up. A project runs one task at a time. While a run is active, the project can’t start another — cancelling releases it, so you can start the next run right away.
Cancelling isn’t admin-only — anyone on the project’s team who can open the task or run can cancel it.
Delete or archive a task
Cancelling stops work, but the task stays on the list with its history. Two related actions clear a task from view:
- Delete removes a task that has never run — one still in the Pending state. A confirmation appears first, and deletion is permanent (a task from a request breakdown can’t be recovered; one from a labelled issue reappears if you re-apply the label).
- Archive hides a Cancelled task from the task list while keeping its run history and cost. It takes effect immediately, without a confirmation step, and the task stays available under the Archived filter.
For the full walk-through of both, see Delete or archive a task.
Starting again after a cancel
Cancelling a run doesn’t end the task. From the task detail page you can start a fresh run whenever you’re ready, and the new attempt begins its own trip through the run states. To pick a task’s work back up after a cancel, see Execute a task.