Antylogic
DemoApp login

399 operational guides

Docs sections
DocsServices
Device

Update One Recurring Service

Update one future Harbor Soho lunch service without changing the rest of the recurring series. Antylogic keeps the parent service recurrence intact and saves the selected date as a single occurrence exception.

In this article

Use this guide when one Soho lunch service needs its own time, visibility, capacity setup or staffing requirement, while the normal weekly service should continue unchanged.

This action is only for the Only this service choice. Future services and delete choices belong to separate recurring-service workflows.

Before you start

  • You are signed in to Harbor Demo Group with Harbor Soho selected.
  • Your role includes service:view, service:manage and staff-schedule:view for Harbor Soho.
  • The selected item is a service event with starts_at, ends_at and a recurrence frequency.
  • The edit form is opened for a specific future occurrence through occurrenceStart.
  • For a public service, valid layout_id and catalog_id values remain selected, such as the Harbor Soho floor plan and Soho Menu.
  • For live captures, use SERVICE_FUTURE_OCCURRENCE_START. The supplied SERVICE_OCCURRENCE_START value, 2026-06-23T12:30:00+00:00, is before 2026-06-25 and is locked as already started.

Instructions

  1. 1.

    Open The Occurrence

    Open the future Soho lunch service from the Services calendar. The edit route must include kind=service and occurrenceStart so the form loads that service day rather than only the recurring parent.

  2. 2.

    Review The Details

    Check the loaded service bundle before editing. If this date was already changed separately, the form is prefilled from the existing exception and shows the single-occurrence notice.

  3. 3.

    Apply The Change

    Change only the fields needed for this occurrence, such as title, time, public or internal visibility, layout, catalogue, staff requirements or related service values.

  4. 4.

    Choose Only This Service

    Press Save. When the Edit recurring service modal appears, choose Only this service. The app sends action=update, scope=single, occurrence_start and the updated bundle to the split endpoint.

  5. 5.

    Confirm The Result

    After saving, return to the Services calendar and refresh the occurrence. The recurring parent remains unchanged, while the selected occurrence is stored as its own non-cancelled exception.

Validations and limits

  • The calendar event must belong to the selected location and have kind service.
  • occurrence_start is required, must be a valid RFC3339 timestamp and must resolve to a real occurrence in the recurrence pattern.
  • Past or already started occurrences cannot be edited.
  • The form requires a title and a valid start/end range.
  • Public services require valid layout_id and catalog_id values.
  • Staff requirement roles must be unique, with valid minimum and recommended counts.
  • Active reservations can block moving the service outside reservation times or changing a reserved public service to internal.
  • Only this service must call POST /api/app/{orgId}/{locationId}/calendar-events/{eventId}/split with action=update and scope=single.
  • The response should include original_id and override_id; the parent recurring series is not truncated or split.

Expected result

The selected occurrence is saved as a calendar_override with the updated window and payload. Antylogic updates or creates the materialised service occurrence for that date, keeps the recurring parent unchanged, refreshes calendar data and returns the operator to the requested calendar route.

Related articles