Reverse a rule run
Takes a run back, undoing the verdicts it wrote. The run transitions immediately, so a second call finds a run that can no longer transition, while the unwinding itself happens in the background.
Rows are left untouched where a verdict was dismissed, where the row sits in a batch that has been reported, and where a later run has taken it over. Each is listed in reversal_summary.
Check reversible before calling. When it is false, non_reversible_reason says why.
Authorizations
Path Parameters
Project friendly ID (e.g. prj_AbCd1234567890Ef).
Rule friendly ID.
Run friendly ID (e.g. rrun_AbCd1234567890Ef).
Response
200
Run friendly ID (e.g. rrun_AbCd1234567890Ef).
running, completed, failed, superseded, reversing, reversed, reversal_failed Where a running run has got to. Null once it is no longer running.
queued, preparing, evaluating What started the run. A run you create here is on_demand.
authoring, ingestion, schedule_sweep, on_demand How many verdicts this run actually changed.
Whether this run can still be taken back.
Why it cannot, when reversible is false.
What a reversal did, once one has run, including the rows it declined to touch and why.
The name of the person who started it. Null for a run started by an account-scoped token, which has no person behind it.