Define which message types cancellation stops
Synthetic cancellation at 15:30 stops booking reminders and arrival instructions that have not been dispatched. It does not delete already-sent messages or suppress the cancellation notice. Queue removal alone is insufficient because a worker may already have selected a message; dispatch must read the booking’s cancellation state.
| Message | State at 15:30 | Purpose | Action |
|---|---|---|---|
| N-C1 | Sent at 14:00 | Booking reminder | Retain history |
| N-C2 | Selected; not dispatched | Arrival instructions | Suppress at dispatch check |
| N-C3 | Queued | Cancellation notice | Continue notification path |
Close obsolete message work
- Record cancellation and its effective booking revision.
- Cancel queued reminders and mark selected unsent messages as suppressible.
- Verify active state at dispatch and record suppressed or sent outcome by purpose.
If a message already left the system before cancellation, record it as sent; do not pretend a later status edit recalls it.
Which of the three messages still needs delivery work?
Show the worked answer
N-C3, the cancellation notice. N-C1 is historical, and N-C2 must be suppressed before dispatch.
A failed cancellation notice leaves a communication task; it does not undo the booking cancellation or restart reminders.