Retry a failed data feed run
Reruns a failed data feed run from the step that failed. Cleans up any partial state from the prior attempt before restarting. Only failed runs are retryable. A collection failure on an upload source is retryable once the upload has been stored; if the run has no stored file, upload it again instead.
The endpoint transitions the run’s status to retrying and enqueues the retry job; the run then moves through the normal lifecycle.
Cleaning up the prior attempt is a revert, so a retry inherits the reverse endpoint’s rules: a run whose data points have been used by a model run cannot be cleaned up, and the retry job returns it to failed with the reason in error_message. Requires the write:data_feed token scope.
Authorizations
Path Parameters
The data feed's friendly ID (e.g. datafd_aBcD1234eFgH5678).
The data feed run's friendly ID (e.g. run_aBcD1234eFgH5678).
Response
Retry initiated; returns the run in retrying state.
A data feed run.
The data feed run's friendly ID.
"run_aBcD1234eFgH5678"
The data feed's friendly ID.
"datafd_aBcD1234eFgH5678"
collection, transformation, publication, completed running, failed, retrying, reversing, reversed, reversal_failed, paused, complete Why the run failed, or why a retry or revert was refused, or null.
The steps created so far, in stage order.
Number of events the run has created.
When collection started; null until a worker picks the run up.