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.
200Data pipeline event retry was successfully initiated
400Cannot retry: file source not available
409Event cannot be retried (not in retryable status)
422Export refused before creating a run; errors[].code identifies the reason
500Data pipeline event retry failed to execute