Recover or deliberately stop background work
Purpose
Provide recovery and stopping semantics that preserve the history of the original work.
How It Works
The shared engine supplies retry and cancellation operations to owning modules. Retrying creates a separate job and preserves the link to the earlier attempt. Completed step keys let the workflow avoid repeating successful work. An HQ operator can retry failed workspace provisioning after confirming the action. The button’s permission differs from the permission the receiving operation checks, which can cause a refusal. Cancellation records the request before attempting to stop execution. A requested abort then settles as cancelled rather than as an ordinary failure. No current Platform route or screen exposes that cancellation flow to a person.
Relationships
The job record supports reconciliation, notices and both monitors; owning modules retain responsibility for the work itself.