Schedule lifecycle

The Lifecycle

Transitions Explained

The subject’s module saves recurrence in its own record transaction. Definition changes recompute future timing, and enabling a paused schedule clears its pause and failure count. The workspace zone fills an unspecified time zone.

Claims choose a due occurrence and move timing forward. The history row can have multiple execution attempts. Success resets consecutive failure, failure increases it and skipped work leaves the count unchanged. Five failures pause an enabled schedule; the dispatcher can also pause an invalid saved definition.

What Cannot Happen

Disabled and paused schedules receive no new claims. They do not resume without an owner save, but existing claimed runs are not cancelled by disablement. Deletion removes history through cascade; no database guarantee establishes that a schedule is removed whenever every possible owner is removed.

Concurrency and Timing

A minute rule drives bounded claim passes. Missed recurrence can be skipped rather than replayed individually, and the two-invocation consumer cap lets excess messages wait. The tested spring gap shifts a scheduled early-morning occurrence forward by an hour. Pausing is visible in owner summaries and history, with no examined attention notice.