Bulk run lifecycle

The Lifecycle

Transitions Explained

This state model describes population-run execution, including a simulation’s underlying comparison run. Failed runs keep already committed page data. Cancellation and automatic retention cleanup are not available deployed behaviors.

What Cannot Happen

Settled runs do not restart; retries use the current running or settled result. Expiry has no outgoing transition. Failure cannot be changed to success by restarting the same run.

Concurrency and Timing

Page evaluation can repeat, but a locked cursor guard commits its counts only once. Restarted execution resumes at the stored cursor. Reserved task concurrency is two; separate interactive starts create separate runs.