Resume or cancel a run

A run that pauses itself when the team balance runs out holds its work without losing progress — resume it to continue each item from the node where it stopped, or cancel it to end the run for good, using the Resume and Cancel buttons on the deployed pipeline's bottom toolbar.

A deployed run does not always run straight through to completion. If your team balance stops covering the work, the run pauses itself and holds its progress. Resume it to continue each item from the node where it stopped, or cancel it to end the run for good.

Resume and Cancel are in the UI, on the deployed pipeline’s Pipeline tab. They sit on the bottom toolbar, with Clone and Export inside its More pipeline actions menu. Resume appears on the toolbar only while the run is paused, and also on the run’s top-up banner once your balance covers the remainder. You cannot pause a run yourself — pausing is something the platform does when funds run out. The agent cannot resume or cancel a run. You do that here.

Before you start

You need a run whose deploy has finished. Resuming and canceling act on a live run, so the buttons appear only after the deploy completes. They also disappear once cancellation starts, once the deploy has failed, and once the run enters its finalization phase with every item in a terminal state. Resuming exists only in the UI; canceling is also available over the public API. Open the run’s Pipeline tab to reach them.

When a run pauses itself for funds

When your team balance can no longer cover the next node’s cost, the run pauses on its own and a banner shows how much to top up. Pricing and billing covers funding and this automatic pause.

The run stops handing out new work, but work already underway continues. An item partway through a node finishes that node, then holds before the next one. Because mid-node work always completes, exactly one more node per item can finish around the moment the run pauses. Items that have already finished are unaffected — no work in progress is lost.

You can tell the run is paused: Resume appears on the toolbar, each held item shows a Paused badge, and a paused: N chip appears among the item filters. The progress bar above them counts only finished items, and shows the paused share as a percentage on hover.

A pause does not refund work already done. The work that finishes right as the run pauses is billed pay-as-you-go like any other work — see Pricing and billing.

Resume a run

Resume appears only while the run is paused. On the run’s banner it appears once your balance covers the run’s worst case, not just the expected remainder — so top up, then resume. Click Resume and confirm the prompt. Every paused item continues through the pipeline from the node where it stopped, and finished items are untouched. The unpaid node is retried, so no item is skipped.

While the resume is starting, the toolbar shows Resuming…, and Resume is not available again until it settles.

Cancel a run

Cancel works on a run that is either in progress or paused. Click it, then confirm the prompt. To back out, click Keep Running. Unlike a pause, canceling actively stops the labeling task at the node: only an expert already holding a task finishes it, and everything else stops where it is. A Code or Match node partway through finishes and the item is then canceled. Items not yet started on their next node are canceled right away.

Canceling a paused run cancels its paused items without resuming them. It does not restart the run.

Label a large dataset in batches — the batch cycle these run controls belong to
Pricing and billing — funding a run, and the automatic pause when the balance runs out