Data Job Lifecycle

The Lifecycle

Transitions Explained

Submission creates validating or queued work directly; accepted is declared vocabulary. Validation saves impact and versions without business writes. Approval checks the saved digest, deadline and any deletion phrase before requeuing the same input. Settlement writes the resulting state directly rather than persisting completing.

Operator pause, retry and cancellation use the transition table. Automatic refusal-rate handling can pause a validation even though the declared table excludes that move. Blocked work may reopen a job that completed with rejections.

What Cannot Happen

Controls refuse final-state resumes and late preview application. Operator pause is unavailable during validation, but the automatic guard has a separate path. Cancellation preserves earlier business commits.

Concurrency and Timing

Controls and settlement use the job lock, while execution stops at batch boundaries. Preview expiry becomes visible when a late approval or explicit expiry action records it; no scheduled sweep closes previews.