Revert a data feed run
Asynchronously reverts a data feed run — reverses its publication, deleting any events, derived data points, and orphaned evidence that the run produced. Reversible runs are:
completeruns (full lifecycle revert)failedruns past collection that have published events (partial publication cleanup)reversal_failedruns (retrying a revert that errored)
A run already reversing or reversed returns 200 with its current state and starts nothing new, so a client that times out can repeat the request and read status. A run in any other state returns 422 “Pipeline run cannot be reverted”. A run whose data points have been used by a model run is not reversible either and returns 422 naming those model runs; free the data points first.
Otherwise the run moves to reversing and the revert continues in the background. Poll GET /data_feeds/{data_feed_friendly_id}/runs/{run_friendly_id} until status is reversed, after which the run can be deleted. Model-run use is checked again when the revert runs, so a run used in the meantime lands in reversal_failed with the reason in error_message. A run that stays reversing far longer than expected needs support; repeating the request does not restart it. 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
Revert initiated, or already underway or finished. Returns the run; read status for reversing or reversed.
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.