Skip to main content

Leave Support and Escalation

Summary​

Leave support uses boundary-based triage and role-based escalation without publishing individual contacts or sensitive evidence.

Audience​

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

Overview​

First-line evidence: affected route/operation, UTC time window, safe correlation identifier, response category, current status, scope count, deployment version, and whether direct/compatibility behavior differs. Never collect Leave reasons, medical/supporting-document data, employee identifiers in public channels, credentials, secrets, or raw payloads.

Owners include Leave support/service, HR/Leave product, gateway, Employee integration, Attendance, Workflow, Payroll, Notification, database, messaging, identity/security, and DevOps/SRE. Individual names and on-call coordinates belong in controlled internal systems.

Source References​

  • microservices/src/leave-service/Program.cs
  • microservices/src/gateway-api/Program.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
  • microservices/src/leave-service/Messaging/OutboxRelayHostedService.cs

See Also​

Keywords​

  • Leave operations
  • Leave Support and Escalation
  • Service support

Revision Information​

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