Skip to main content

Troubleshooting Decision Tree

Summary​

An Attendance issue needs classification before deeper diagnosis.

Audience​

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

Symptoms​

  • An Attendance issue needs classification before deeper diagnosis.

Scope​

Safe first-line classification across confirmed scenarios.

Likely causes​

Access/context, capture/punch/calculation/workflow, Time Office, Payroll, event, persistence, or gateway categories.

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. Follow the tree; collect sanitized evidence and use only approved monitoring and read operations.
  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​

Open the linked scenario and apply its safe resolution. Stop and escalate when ownership or state is uncertain.

Resolution​

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

Validation​

Repeat the original safe operation and confirm UI/API plus operational signals.

Evidence to collect​

Selected branch, timestamp, environment, sanitized scope, response category, correlation identifier.

Escalation​

Route to the owner named by the selected scenario.

Source References​

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

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Troubleshooting Decision Tree

Revision Information​

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