Run and result help - Millwork

Start with the run status

Status	Meaning	Next step
`accepted` or `queued`	The run is waiting.	Check every two seconds for up to 90 seconds. Do not submit it again.
`running` or `progress`	Work is in progress.	Check every two seconds for up to 90 seconds.
`completed`	Work finished.	Fetch the result and receipt. Echo has no model result.
`failed`	Work stopped with an error.	Read events, then the receipt.
`cancelled`	The run was stopped.	No result is available. Read the receipt.
`expired`	The run passed its allowed time.	No result is available. Read the receipt.

Common problems

What happened	What to do
The connection dropped after submission	Retry with the same `Idempotency-Key` and identical body.
The run is still queued or running after 90 seconds	Stop polling, keep the run ID, and check again later. Do not create another run to replace it.
The run completed but result returns `404`	Check the mode and `retention_expires_at`. Echo has no result. A retained result may have expired.
The run failed with `no_eligible_arms`	Refresh the catalog and confirm the registered option supports the requested data class.
A provider attempt failed	Use its safe reason in Provider connection help.
Requested and reported model names differ	Compare both values in the result or receipt. A reported snapshot name is not automatically a fallback.
The cost limit was reached	The limit can stop another provider attempt. It cannot cancel or reverse a call already in progress.

Result and receipt

The result contains model output. The receipt records how the run was handled and does not copy the prompt or output. Keep the execution_id. It connects the status, events, result, receipt, and support request.

Retry safely

Recover without starting the same work twice.

Stop a run

Cancel work you no longer need.

⌘I