Antylogic
DemoApp login

399 operational guides

Docs sections
DocsService calendars
Device

Update Future Recurring Services

Apply edits to a recurring service from one selected future occurrence onwards. Antylogic keeps the earlier part of the series on the original service and creates a new future service series with the saved changes.

In this article

Use this guide when a location manager needs a recurring service change to begin at one selected future occurrence, such as Soho lunch service at Harbor Soho.

The save is a scoped recurrence decision: choosing Future services shortens the original series and creates a follow-up service bundle for the future segment.

Before you start

  • You are signed in to Harbor Demo Group with Harbor Soho selected.
  • You can view and manage services for the location.
  • The service is recurring and the selected occurrence is in the future.
  • The edit screen was opened from a specific occurrence in the Services calendar.
  • For a public service, a valid layout and catalogue remain selected.
  • Staff roles and staff members already exist before saving required roles or staff schedule rows.
  • You can manage staff schedules if staff schedule rows are saved.
  • You can use reservation automation if an optimisation configuration is included.

Instructions

  1. 1.

    Open the future occurrence

    Open the Services calendar and select the future occurrence that should start the change. The route must include kind=service and occurrenceStart so Antylogic can anchor the edit to that occurrence.

  2. 2.

    Review the loaded service

    Check the service details, required roles, staff and repeat settings. The editor loads the service bundle for the selected occurrence_start, including recurrence, capacity references and staffing data.

  3. 3.

    Make the future changes

    Edit only the details that should apply from the selected occurrence onwards. Public services need a layout and catalogue; internal services are planning blocks and do not need layout, catalogue or optimisation references.

  4. 4.

    Choose Future services

    Press Save and choose Future services in the recurrence scope modal. Cancelling sends no update, and Only this service belongs to the single-occurrence path.

  5. 5.

    Confirm the updated calendar

    After saving, Antylogic returns to the Services calendar. The original recurring service ends just before the selected occurrence, and the new future service series starts from that occurrence with the saved details.

Validations and limits

  • Past or already started occurrences are locked and cannot be edited with future scope.
  • The save sends POST /api/app/{orgId}/{locationId}/calendar-events/{eventId}/split with action=update, scope=future, occurrence_start and the edited bundle.
  • The result includes original_id and future_id, plus optional operation_warnings shown after a successful save.
  • Changing reserved future public occurrences to internal is blocked.
  • Moving reserved future occurrences outside their reservation times is blocked.
  • The inspected future-scope path range-checks occurrence_start, but this package did not prove that the timestamp must exactly match a generated recurrence instance.

Expected result

The earlier part of the recurring service stays on the original calendar event, while the selected future occurrence and later occurrences are handled by a new follow-up service series.