Retry a failed run
POST/api/v1/runs/{id}/retry
Creates a new pending attempt linked to the failed run after EXECUTE permission. Retry restarts from the beginning and is not resume behavior. Protected mutations require the session cookie and CSRF header.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Failed run identifier.
Responses
Section titled “Responses”Retry attempt accepted
Public durable run state and attempt lineage. Lease tokens and resolved datasource security are never exposed.
object
One-based attempt number.
Earliest database time at which this attempt is eligible for claim.
Mode-specific warning about sink state after cancellation.
Incremental watermark committed only by successful finalization.
Run creation timestamp in UTC.
Elapsed execution time in milliseconds when reported.
Credential-redacted failure detail.
Worker identity assigned after claim.
Terminal completion timestamp in UTC.
Most recent successful worker heartbeat in UTC.
Run attempt identifier.
Owning job definition identifier.
Current claim expiry timestamp in UTC.
Previous attempt in the retry chain.
Rows processed by this attempt when reported.
Execution start timestamp in UTC.
Durable lifecycle state.
Authentication is required or credentials are invalid.
RFC 7807 problem response. Dynamic detail text is credential-redacted.
object
The authenticated identity lacks the required permission.
RFC 7807 problem response. Dynamic detail text is credential-redacted.
object
The requested resource does not exist or is not visible.
RFC 7807 problem response. Dynamic detail text is credential-redacted.
object
The request conflicts with the current resource or run state.
RFC 7807 problem response. Dynamic detail text is credential-redacted.