Recalculation run

The Lifecycle

Transitions Explained

Only running, completed and failed are persisted statuses. The start request records or selects a run and executes a short series of batches. Remaining work reaches a worker through captured events. The worker advances transactional progress and requests another delivery when its budget expires. Retryable failures preserve committed progress and attempt to store a redacted reason.

What Cannot Happen

Terminal runs do not reopen through regional operations. There is no cancellation action. Final delivery failure does not guarantee failed status: settlement is best effort, and an error during settlement can leave a run stuck in running.

Concurrency and Timing

Run locks prevent committed batches from repeating. Record locks coordinate saves during processing. The console polls an adopted running run every one and a half seconds, but it does not display monitoring errors or restore failed historical runs after reload.