Antylogic
DemoApp login

399 operational guides

Docs sections
DocsAttendance
Device

Delete manual attendance

Remove an existing manual attendance record from the selected location. In Antylogic this record is stored as a staff_shift calendar event, and deletion permanently removes it from attendance and calendar views.

In this article

Manual attendance is deleted from the staff shift calendar-event editor. The correct product flow uses calendar-events, because the attendance record is a calendar_events item with kind=staff_shift.

Use this guide when a manager has found an incorrect manual attendance entry at Harbor Soho and needs to remove it completely from the operational attendance record.

Before you start

  • Signed in with Harbor Demo Group and Harbor Soho selected.
  • The user can manage staff shifts for Harbor Soho.
  • A staff_shift calendar event exists for Harbor Soho with a known event id. For the GB guide and captures, use Olivia Hart with payload.source=manual.
  • Open the existing event from the calendar, attendance surface, or direct editor route calendars/edit/:eventId?kind=staff_shift.
  • Use the calendar-events delete flow for this action, not the legacy staff shift endpoint.

Instructions

  1. 1.

    Open the attendance event

    Open the existing manual attendance event. The editor loads GET /api/app/{orgId}/{locationId}/calendar-events/{eventId} and should show an existing staff_shift record in edit mode.

  2. 2.

    Check the record

    Confirm the staff member, date, start time and end time before deleting. The delete action itself does not check payload.source, so the operator must verify that this is the intended manual attendance entry.

  3. 3.

    Open the delete confirmation

    Select Delete on the event form. The app opens the Delete event confirmation and warns that Attendance will be removed permanently. Cancel closes the modal and leaves the record unchanged.

  4. 4.

    Confirm deletion

    Select Delete in the modal. The app sends DELETE /api/app/{orgId}/{locationId}/calendar-events/{eventId}; the backend requires staff-shifts:manage and checks that the event belongs to the selected location.

Validations and limits

  • Delete is only available for an existing event id in edit mode.
  • If the event is missing or is not kind=staff_shift, the form treats it as not found.
  • The selected organisation and location must be present in the app context.
  • A successful delete removes the calendar_events row and returns 204 No Content.
  • The delete operation does not validate payload.source=manual; use a verified manual staff_shift event for documentation and training.
  • In the corrections table, row-level Delete is disabled while a correction is pending.
  • Do not document DELETE /api/app/{orgId}/{locationId}/staff/{staffId}/shifts/{shiftId} as the path for this action.

Expected result

The manual staff_shift attendance event is permanently removed, calendar and attendance data refresh, and the app returns to the configured route. If the API request fails, the form remains open and shows the error message.

Related articles