Skip to main content

Attendance Troubleshooting

Summary​

An Attendance incident needs safe triage across access, tenant context, workflows, dependencies, or compatibility routing.

Audience​

Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.

Symptoms​

  • An Attendance incident needs safe triage across access, tenant context, workflows, dependencies, or compatibility routing.

Scope​

All confirmed Attendance and Time Office support scenarios listed below.

Likely causes​

Authentication/context failure, invalid workflow input, unresolved policy context, Payroll dependency, outbox delivery, persistence startup, or compatibility routing.

Cause​

The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.

Safe diagnostic steps​

  1. Select the matching scenario page; identify the affected route, tenant-safe employee reference, date/period, correlation identifier, and observed HTTP category. Check process health and approved telemetry. Do not inspect secrets or alter production data.
  2. Preserve tenant isolation and redact personal or security-sensitive data.
  3. Do not use direct database changes, authorization bypasses, or ad hoc broker operations.

Safe resolution​

Correct valid user input or access through approved administration, restore the owning dependency, or escalate to the named service owner. Never bypass authorization, edit the database directly, or replay broker messages ad hoc.

Resolution​

Apply only the Safe resolution described above and remain within the documented ownership boundary.

Validation​

Repeat the original safe read/action and verify expected UI/API state plus relevant audit or operational signal.

Evidence to collect​

Timestamp, environment, route category, sanitized request context, correlation identifier, response category, and relevant sanitized logs.

Escalation​

Start with Support; route to Attendance, Time Office, Gateway, Payroll, database, messaging, identity/security, or DevOps according to the scenario.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Api/Endpoints.cs

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Attendance Troubleshooting

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly