Skip to Content

Cancelled and hold

Cancelled and hold are honest runtime states. They are not marketing failures. They tell you where the run stopped.

Cancelled

cancelled means the user stopped an active run through the product-path cancel route.

Current proven behavior:

  • the cancel route returns cancelled state for an owned active run
  • one run.cancelled terminal event is emitted
  • late ready-for-review overwrite was checked in proof
  • a normal post-cancel run can still reach ready-for-review

Support wording:

This run was cancelled. Start a new run if you want TARX to continue.

Hold

hold means the run stopped on a blocker that should remain inspectable.

Examples of blocker categories:

  • model timeout
  • runtime fetch boundary
  • unavailable evidence surface
  • missing local prerequisite

Support wording:

This run is on hold because the runtime hit a blocker. Open the evidence surfaces to see what happened.

Do not hide holds

Do not convert a hold state into success copy. The alpha is more trustworthy when blocked work is visible.

Next

Continue to Evidence surfaces.

Agents