Retry a data pipeline run

Retry processing using the run's stored input. Reference-backed retries require the admission receipt described in the request contract; those retries create a linked replacement run rather than resetting the original. A 503 response means the retry state could not be safely established.

Ordinary retries retain stored input. Reference retries require an admissionReceipt from saved reference admission with operation retry and oldEventUuid. They create a fresh linked event after exact old settlement, never reset the old event. Unknown admission or execution returns 503 without replacement.

Path Params
string
required

uuid of data pipeline event

Responses
200

Data pipeline event retry was successfully initiated

400

Cannot retry: file source not available

409

Event cannot be retried (not in retryable status)

422

Export refused before creating a run; errors[].code identifies the reason

500

Data pipeline event retry failed to execute

Language
Credentials
OAuth2
Missing 1 required scope
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json