# Safer class edits and cancellations

Class type, room, instructor, time and capacity remain editable inline. Changes
validate the resulting class, and an outdated or conflicting capacity edit asks
staff to refresh before trying again.

Cancelling selected classes applies the class, booking and eligible consumed-credit
changes together. Delivery may be pending or require review after cancellation
succeeds; it does not mean the cancellation failed. Client, course and instructor
messages start with Don't notify and require explicit channels. Monetary refunds
remain a separate reviewed payment action.

A future cancelled class can be reactivated while preserving its old cancelled
bookings. Selected clients are reviewed for new bookings using current eligibility
and availability, with individual confirmed, waitlisted, ineligible or pending
outcomes. Restoration does not send client messages.


If the service cannot confirm whether an action completed, keep the current
review and retry that same action. An unconfirmed result does not mean it was
rolled back. The app must retain its retry identity until the result is known.

Cancellation and Undo now recheck current location access on every attempt.
A previous successful response does not override removed access. Staff with
assigned locations can act on eligible classes at those locations; a schedule
cancellation requires access to its template and every affected class. Undo keeps old
cancelled bookings in history and applies current eligibility to new bookings.

Substitute assignment uses the same canonical occurrence transaction as other
schedule edits. The server rechecks current permission, location, instructor
qualification and conflicts before saving the assignment. Repeated requests use
the same reserved attempt while it is retained. An uncertain result asks staff
to review the saved class before starting another attempt; notification results
remain separate from the saved assignment.