Antylogic
DemoApp login

399 operational guides

Docs sections
DocsReservations
Device

Restore a Cancelled Reservation

Restore a cancelled reservation from the occurrence detail screen so the booking becomes active again, while Antylogic validates the service state and protects automatic optimisation.

In this article

Use this guide when a front-of-house manager needs to reverse an accidental cancellation without rebuilding the reservation from scratch. The restore keeps the reservation context, refreshes the occurrence detail and clears the cancellation state after confirmation.

If automatic optimisation cannot accept the restored booking, Antylogic asks the operator to confirm saving the change in manual mode. The current implementation may still show the fallback Spanish labels `Descancelar reserva`, `¿Descancelar esta reserva?` and `Guardar y pasar a manual` until English translations are added.

Before you start

  • The operator is signed in to Harbor Demo Group / Harbor Soho with `reservation:manage`.
  • The reservation occurrence detail can load the occurrence, reservations, table assignments and customers.
  • The target reservation belongs to Harbor Soho and has status `cancelled`.
  • For the normal path, the occurrence is not completed and is not in `booking_mode` `waiting_list` when restoring the cancelled reservation to booked.
  • For documentation captures, prepare a cancelled recoverable reservation in the disposable GB runtime; the supplied runtime does not expose a ready happy-path cancelled reservation.

Instructions

  1. 1.

    Open the reservation occurrence

    Open the Harbor Soho reservations calendar and enter the Soho lunch service occurrence, or use the deep link to the reservation occurrence detail. The detail view should show the reservation list, customers and current assignment context.

  2. 2.

    Find the cancelled reservation

    Locate the reservation that needs to be made active again. The restore action is only relevant for rows or editors where the reservation status is cancelled.

  3. 3.

    Start the restore action

    Choose the uncancel action on the cancelled reservation. In the current UI, the fallback action label is `Descancelar reserva`; use the English localised label in the guide once translations exist.

  4. 4.

    Confirm the restore

    The confirmation modal identifies the customer and asks the operator to confirm that the cancelled reservation should become active again. Closing the modal leaves the reservation cancelled.

  5. 5.

    Review the refreshed detail

    After confirmation succeeds, Antylogic refreshes the occurrence detail. The reservation is active again, the cancellation timestamp is cleared and the editor closes if the action started there.

  6. 6.

    Handle manual mode if requested

    If Antylogic shows the manual confirmation modal, the operator can select `Guardar y pasar a manual` to save the restored reservation and switch the occurrence to manual mode, or close the modal to leave the reservation cancelled.

Validations and limits

  • The restore action is available only to operators with `reservation:manage`.
  • The row action is disabled unless the reservation status is `cancelled` and the occurrence is not completed.
  • The editor footer only shows the restore action for a cancelled reservation that can be restored.
  • Confirming the normal restore sends the reservation update with status `booked`.
  • The normal restore action does not ask the operator to choose tables and does not promise restored table assignments.
  • If the backend returns `error.optimization.manual_confirmation_required` with code `6200`, the operator must explicitly accept manual mode before the restore is saved.
  • Do not use the existing cancelled waitlist reservation as the happy-path example; cancelled to booked is rejected in `booking_mode` `waiting_list`.
  • Do not document a success toast for this action; the verified feedback is the closed modal or editor and the refreshed reservation detail.

Expected result

The reservation returns to booked status, its cancellation state is cleared and the occurrence context is reloaded. If manual mode was confirmed, the occurrence optimisation state is invalidated and the occurrence can show manual mode.

Related articles