Switch a service occurrence back to automatic mode

In this article

Before you start

• You are working in Harbor Demo Group at the Harbor Soho location.
• The service occurrence detail screen is open for `/:orgId/:locationId/reservations/:occurrenceId`.
• The occurrence is a future service occurrence, open for acceptance, currently Manual, and backed by a valid layout and optimisation configuration.
• Your user can manage reservations and has access to automatic reservation features.
• The optimisation backend is available so the recalculation can complete.

Instructions

1. 1.

   Open the occurrence

   Open the Harbor Soho service occurrence you want to return to automatic management. Confirm that the detail screen has loaded reservations, table assignments, layout, and optimisation context.

2. 2.

   Confirm the action is available

   Check that the occurrence is Manual, open, future-dated, and has optimisation configuration. The automatic-mode action is hidden for Automatic, Waiting list, completed, past, or unconfigured occurrences.

3. 3.

   Open Settings

   Open Settings on the occurrence detail screen. The current app labels may appear as `Configuraciones` and `Pasar a modo automatico`; in English documentation, refer to them as Settings and Switch to automatic mode.

4. 4.

   Switch back to automatic mode

   Select Switch to automatic mode. Antylogic closes the menu, changes the occurrence booking mode to Automatic, and starts a forced optimiser recalculation.

5. 5.

   Wait for recalculation

   Wait for the detail screen to refresh. The optimiser uses active reservations and current assignments, excluding cancelled and waiting-list reservations from the optimisation payload.

6. 6.

   Review the final state

   Review the mode badge and proposed arrangements. The normal result is Automatic with fresh optimiser output, but the occurrence can also become completed or enter Waiting list mode if the optimiser and waitlist rules determine that outcome.

Validations and limits

• Users with reservation viewing access can open the detail screen, but this action requires reservation management access and automatic reservation feature access.
• The action only appears when the occurrence is Manual, open, future-dated, and has an optimisation configuration.
• The forced optimiser run prevents Antylogic from reusing an existing fresh cached run.
• This action recalculates and stores optimiser output only; it does not apply a proposed table distribution to table assignments.
• Waiting list is a derived outcome here, not a mode the operator can choose from this Settings action.
• The mode change and optimiser run are separate operations, so a failed optimiser run after the mode change can leave the refreshed occurrence back in Manual with a failed optimisation status.

Expected result

The occurrence returns to automatic reservation management with a fresh optimisation run available for review. Proposed table arrangements remain proposals until an operator applies a solution in a separate flow.