Rerun Pipeline

Re-run a finished pipeline from a chosen phase onward. Earlier phases reuse their stored cells; prior human review decisions are preserved.

Re-run a finished pipeline from a chosen producing phase onward. The named phase and everything after it re-execute; every phase before it reuses its stored cells untouched. This is how you re-resolve or re-validate a run after tuning a policy or a gate, without paying to re-extract documents that already extracted cleanly.

Every document must be terminal before a rerun. A run with documents still processing is rejected with 400. The rerun resets field states so the phase loop sees active fields again, but prior human decisions in the review decision log survive: a gate a reviewer already approved or overrode does not re-block. A blocking validation gate positioned before the rerun start keeps its blocked fields, since that gate is not re-executed.

The from_phase value must be one of transfer, extraction, resolution, or validation, and the run must actually contain a phase of that type. Re-running from resolution re-resolves and re-validates while keeping extraction; re-running from validation re-validates only. After a rerun finishes, recreate the data product to rebuild its review queue. This endpoint requires an API key with the write scope.

Response

{
  "enqueued": 24,
  "fromPhaseIndex": 2
}

Errors