Data Run Lifecycle

The Lifecycle

Transitions Explained

Start can begin registered work or take up paused work. Resume specifically requires paused state. Each running read can poll jobs and submit eligible datasets. Parent success includes finally blocked steps, making readiness a separate result. Pause leaves child jobs active; cancellation asks them to stop before settling the parent.

What Cannot Happen

Final runs do not restart. Pausing a registered run is refused. Neither failure nor cancellation compensates the load.

Concurrency and Timing

There is no background driver or saved staff token. Concurrent passes and failed child bookkeeping can duplicate submissions. Logged cancellation errors can leave child jobs active after the parent has ended.