Re-evaluate a rule over a period
Runs the rule again across a period you name, and returns the run so you can follow it.
You do not need this after writing an event, applying a batch correction or setting a data point value. Each of those already re-evaluates the records it touched. Reach for it when a rule was fixed after the fact, or when data changed underneath a period that has already been evaluated.
Both bounds are required. The dashboard treats a missing bound as unbounded, but a script that omitted one would silently widen the run to the project’s whole history, so here an absent bound is refused.
A run that completes without changing a verdict is a normal outcome, not a failure.
Authorizations
Path Parameters
Project friendly ID (e.g. prj_AbCd1234567890Ef).
Rule friendly ID.
Body
Response
201
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.