Notify Participants After Meeting Changes
What It Does
A staff or series write calls, reschedules, publishes or cancels a meeting. The delivery work commits with the business change. A skip can still leave participants uninformed, because only reminders have a recurring recovery path. Dissolution suppresses cancellation notices, and returning a scheduled meeting to draft sends no withdrawal.
The Flow
Validate and lock the meeting at the supplied version, then save it; creation also copies the dated roster. Persist the corresponding business event with the meeting change. Reserve each recipient’s notice key and submit the request using their CRM address; cancellations include declined participants. Append any needed room creation, update or cancellation request. Wake the event and communication dispatchers after the transaction commits.
When Something Fails
Reject the request without committing changes. No partial database change. Roll back the transaction. No committed event or change. Release the key and log an unavailable address or communications service; other database failures abort the write. Non-reminder notices have no scheduled recovery after a skip. Abort the enclosing write. No room request survives rollback. Treat the wake-up as best effort; scheduled dispatch remains available. Delivery waits for a later dispatcher pass.
Open Design Questions
The delivery work commits with the business change. A skip can still leave participants uninformed, because only reminders have a recurring recovery path. Dissolution suppresses cancellation notices, and returning a scheduled meeting to draft sends no withdrawal.