Run data to preserve
- Who started the run
- Active company or active tenant
- Selected schemas for source shape
- RuleSet or rules used for comparison logic
- Source inputs
- Processing status
- Generated output references
- Error details when processing fails
Status interpretation
Pending and Running are the active statuses. The remaining five are terminal: a run in any of them is finished, will not change status again, and triggers run-completion alerts.
Stage sequence
A run advances through stages in a fixed order. The current stage is exposed on live run status and identifies where a run is spending time or where it stopped.Failure visibility
A failed run stays visible rather than disappearing. Runs that failed after the most recent completed run are grouped under Needs Attention in run history, and a run that failed before producing any output file is still listed — a failure with no artifact is a result worth seeing, not an absence.Review principle
Treat the run as evidence. If you change schema, mapping, source files, or rules, create a new run instead of overwriting the old result.To start a run, see Run a reconciliation.