Attendance Support and Escalation

Summary

Escalate by affected boundary and collect only sanitized evidence.

Audience

• First-line support, service owners, DevOps/SRE, security, and product owners

Escalation flow

First-line checks: authentication/tenant context, intended route, time range, current UI/API error category, process health and whether the issue is isolated. Collect timestamps, safe tenant reference, route family, correlation/trace identifiers, sanitized request shape, response status/category, screenshots with synthetic/redacted data, and relevant outbox/audit state.

Never include tokens, credentials, configuration values, personal Attendance details or exploit information. Security or cross-tenant symptoms follow the security escalation path immediately.

Source References

• microservices/src/attendance-service/Program.cs
• microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/docs/attendance-shift-cutover-runbook.md

Related Articles

• Attendance operations
• Attendance troubleshooting
• Attendance technical documentation

See Also

• Attendance database documentation
• Attendance events documentation

Keywords

• Attendance operations
• Support
• Reliability

Revision Information

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