Skip to main content
Start with the last returned job or request key. Read its current state before submitting anything else. Provide the last job link, ID or saved receipt if this is a new conversation. What you get: An evidence-based recovery of the existing work and its resulting state. The steps below describe the workflow your agent follows and the results to verify.

Read state at the right layer

dataset_transfer reports byte transfer and publication. dataset_run reports landing. dataset_pipeline reports transformation execution. Completing one does not complete the others. Follow poll_after_seconds or the returned polling guidance while work is active. A queue wait does not prove a worker is stuck. Read terminal receipts once and follow their next actions rather than continuing to poll indefinitely. An observation timeout does not establish remote cancellation. If a provider might have accepted a request, use its saved identity for reconciliation. Do not infer from a disconnected client that paid work never started.

Cancel with the owning control

Use the exact pipeline-run cancellation for a transformation, cancel_dataset for its supported dataset work, and cancel_finetune for training. Cancellation can prevent publication or record provider intent without instantly terminating remote computation. After recovery, verify the output and its identities before declaring success. Preserve previous successful versions and frozen consumer inputs.