Distinguish series and occurrence identity
Synthetic series S-R meets every Tuesday at 18:00 for three listed occurrences in October 2026. Only occurrence O-R2 moves to Wednesday at 19:00. It keeps its occurrence ID and receives a revision; the series rule and the other two occurrences remain unchanged. Customer acceptance is handled separately where the agreed policy requires it.
| Occurrence | Original | Exception | Resolved schedule |
|---|---|---|---|
| O-R1 | Tue 6 Oct 18:00 | None | 6 Oct 18:00 |
| O-R2 | Tue 13 Oct 18:00 | Move to Wed 14 Oct 19:00 | 14 Oct 19:00 |
| O-R3 | Tue 20 Oct 18:00 | None | 20 Oct 18:00 |
Resolve bookings through the occurrence exception
- Select O-R2 explicitly; do not edit the series weekday or start time.
- Save its new schedule and revision, retaining the original values.
- Review O-R2 bookings, eligibility and pending reminders against the revised start.
If a booking cannot accept the change, preserve its response and route it to rescheduling or operator cancellation.
Does changing O-R2 move O-R3 to Wednesday too?
Show the worked answer
No. O-R3 remains Tuesday 20 Oct 18:00. Only the selected occurrence has an exception.
Future regeneration must apply the stored exception rather than recreate O-R2 at its original series time.