Antylogic
DemoApp login

399 operational guides

Docs sections
DocsReservations
Device

Confirm manual table mode

Save a table assignment that cannot stay automatic by confirming the retry that switches the service occurrence to manual mode.

In this article

Use this guide when a table change for an open automatic service cannot be accepted by the optimiser. The confirmation is an explicit operator decision: save the selected tables and take that occurrence out of automatic planning.

In the en-GB demo, the documented case is Harbor Demo Group, Harbor Soho, the Soho lunch service, reservation Liam Scott, and tables T2 and B1.

Before you start

  • The operator is signed in with active `ORG_ID` and `LOCATION_ID` for Harbor Soho.
  • The operator has `reservation:view` to open the service detail and `reservation:manage` to save or confirm table changes.
  • The service occurrence is open and currently in `automatic` booking mode.
  • The reservation belongs to the active location and is not in `waitlist` or `cancelled` status.
  • The full table set to save is selected. In the en-GB demo, use `BOOKING_TABLES_MANUAL_TABLE_1` T2 and `BOOKING_TABLES_MANUAL_TABLE_2` B1 for Liam Scott.

Instructions

  1. 1.

    Open the service occurrence

    Open the reservation occurrence for Harbor Soho from the reservations calendar or by deep link. For the demo capture, use `BOOKING_TABLES_MANUAL_OCCURRENCE_ID` for the Soho lunch service.

  2. 2.

    Open the reservation editor

    Go to the service timeline and open Liam Scott's reservation. Start the table assignment change from the reservation editor or the assignment board.

  3. 3.

    Select the manual table allocation

    Change the table mode to assigned tables, open the table selector, and select T2 and B1 in the Harbor Soho layout. Return to the editor with both tables selected.

  4. 4.

    Save the first attempt

    Press Save. Because the service is open and automatic, Antylogic checks whether the optimiser can still keep a valid automatic plan before writing the new table distribution.

  5. 5.

    Review the confirmation

    If the optimiser rejects the first attempt with code `6200`, the app shows the manual-mode confirmation. Cancelling or closing it clears the pending retry and does not save the attempted table change.

  6. 6.

    Confirm manual mode

    Confirm the prompt. The app retries the same save with `confirm_manual_mode: true`, saves T2 and B1 as the reservation's manual table assignment, and switches the occurrence to manual mode.

  7. 7.

    Verify the result

    After the retry succeeds, the page refreshes the occurrence, reservations and assignments. The prompt closes, the service shows Manual mode, and Liam Scott keeps the selected tables assigned.

Validations and limits

  • Table-save controls are available only when the operator has `reservation:manage`.
  • The first save attempt is sent without `confirm_manual_mode`.
  • The confirmation appears only when the API error payload has numeric code `6200`; it does not depend on translated text.
  • The retry uses the same `table_ids` and adds `confirm_manual_mode: true`.
  • The table replacement is total: previous `reservation_table_assignment` rows are removed and the new rows are written with `manual_fixed` assignment mode.
  • If `confirm_manual_mode: true` is sent outside an open automatic occurrence, the API behaves like a normal replacement and does not force manual mode.
  • Waitlist reservations cannot receive table assignments through this flow.
  • If the confirmed retry fails, the app reports an error and the operator should not assume the change was saved.

Expected result

The reservation keeps the selected tables, the service occurrence changes to manual mode, the optimisation cache for that occurrence is cleared, and no new automatic optimisation run is triggered for that confirmed mutation.

Related articles