How the problem develops
A client moves a session but the old invite and reminder remain active. Someone turns up at the original time, while another person sees two bookings. The new appointment was created successfully, but the old state was never reconciled.
What to check first
- Trace the booking identifier across calendar events, reminders and the client record.
- Check what happens when cancellation succeeds but creation of the replacement fails.
A better process
- Link old and replacement times to one booking reference.
- Update or cancel the previous calendar event and its pending reminders.
- Keep a visible recovery state if either side of the change fails.
What a system can do
Apply permitted changes, refresh the invitation and stop obsolete reminder jobs once the update is confirmed.
Where people stay in control
Requests outside the rescheduling policy, urgent priorities and fee disputes need a person.
Benefits and tradeoffs
The useful outcome
The customer and team can identify the current appointment unambiguously.
The tradeoff
Connected calendar services can fail independently. Recovery must avoid silently losing both the old and new appointment.
Test before going live
Reschedule twice, repeat the same event notification and simulate one failed calendar update. Check every attendee’s visible invitation and reminder state.