Recurring Series Status
The Lifecycle
active: Materialization fills missing occurrence dates in an eighteen-month rolling window.
paused: Materialization makes no new meetings; a pause edit cancels future editable occurrences.
ended: Materialization stops, but staff may still reactivate or pause the series.
Transitions Explained
Staff pause the series. The saved series version matches and recurrence and zone remain valid. The subsequent rewrite cancels future draft or scheduled occurrences, notifying called meetings.
Staff resume the series. The saved series version matches and the updated rule remains valid. Create missing dates without restoring dates already represented by cancelled meetings.
Staff end the series or its committee is dissolved. Staff compares the series version; dissolution acts inside its own transaction. A staff edit cancels future editable occurrences; dissolution sets an end date and silently cancels later committee meetings.
Staff end a paused series or its committee is dissolved. Staff compares the series version; dissolution acts inside its own transaction. Stop materialization and retain the earlier applicable end date on dissolution.
Staff reactivate an ended series. The version and updated rule pass validation; no terminal-state refusal is implemented. Materialize active dates that have no existing occurrence.
Staff pause an ended series. The version and updated rule pass validation; no terminal-state refusal is implemented. Create no new dates and cancel any remaining future editable occurrences during rewrite.
What Cannot Happen
No transition between the three declared statuses is refused solely because of its previous status. The recorded product policy for restoring paused dates and preserving manually moved occurrences remains unimplemented.
Concurrency and Timing
A materialization locks its series, but series saving and materialization are separate transactions. The daily pass isolates each series failure and database occurrence uniqueness prevents duplicate dates.