Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTeam
Device

Create a Location Holiday Closure

Create an all-day closure for Harbor Soho across a full date range. The closure is saved as a location_vacation calendar event and appears afterwards in the holidays calendar.

In this article

Use this flow when the whole location is closed for holidays or for an operational shutdown. It creates a location-level calendar event, not an employee holiday, so no staff member is assigned.

The guide is written for managers working in the Harbor Demo Group / Harbor Soho GB demo context. The closure uses the location timezone, Europe/London, and returns to the holidays calendar after a successful save.

Before you start

  • You are signed in with Harbor Demo Group selected and Harbor Soho as the active location.
  • Your role has vacation:manage for Harbor Soho. View-only holiday access and vacation:request are not enough to create a location closure.
  • Choose a complete full-day date range with no active reservations and no booked service occurrences that overlap the closure.
  • Use the GB demo session for captures: en-GB locale, Harbor Soho, and Europe/London timezone.

Instructions

  1. 1.

    Open the closure form

    Start from the holidays calendar and open a managed holiday entry, then switch on the full-location closure option. Operators can also open the direct creation route /:orgId/:locationId/calendars/create?kind=location_vacation. In closure mode the form is for Harbor Soho itself, so it does not ask for an employee.

  2. 2.

    Set the closure dates

    Enter the first and last closure dates. Antylogic treats the closure as all-day: the start is normalised to 00:00 and the end to 23:59 in Europe/London. Add notes only when the operator needs to record the reason for the closure.

  3. 3.

    Save the closure

    Save the form to create the event. The app submits kind location_vacation with all_day true, no staff member, the selected date range, the location timezone and optional reason notes.

  4. 4.

    Resolve booking blockers

    If active reservations or booked service occurrences overlap the selected range, the save is rejected. Pick another range or resolve those bookings first. The action does not cancel reservations or notify customers automatically.

  5. 5.

    Confirm it in the holidays calendar

    Return to /:orgId/:locationId/calendars/vacations and confirm the Harbor Soho closure appears across the selected days. In other calendar presets, the same event can appear as the location being closed for holidays.

Validations and limits

  • The organisation and location context must be present; otherwise the screen cannot find the requested location and the form cannot be saved.
  • Only vacation:manage can create location_vacation events. vacation:view can list them, and vacation:request only applies to an employee's own staff_vacation request.
  • Start and end dates are required, and the start must be before the end before the app sends the create request.
  • A location closure cannot be recurring; recurrence is only accepted for service and vacation_blackout events.
  • The location_vacation payload only accepts the optional reason string. Other payload keys are rejected.
  • If the timezone is missing, the backend uses the location timezone and falls back to UTC only when the location has no timezone.
  • Active reservations or service occurrences with active reservations block the save with error.calendar.location_vacation.reservations.
  • The regular holidays preset does not show location_vacation as a separate create option, so document the direct route or the staff-holiday toggle path.

Expected result

Harbor Soho has a full-day holiday closure recorded in calendar_events as a location_vacation event. The closure appears in the holidays calendar, can block later services or private events during the same range, and may remove overlapping unbooked service occurrences while it is created.

Related articles