Skip to main content

Leave Troubleshooting

Summary​

Safe source-backed triage entry point for Leave UI, service, dependency, data, event, and gateway issues.

Audience​

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

Symptoms​

A Leave user or operator reports an access, request, calculation, decision, balance, calendar, integration, data, or routing problem.

Scope​

Use this section to classify the affected boundary before opening detailed guidance.

Cause​

The cause must be confirmed from current state and source-backed evidence.

Likely causes​

  • Authentication/tenant/employee context
  • Leave validation or request state
  • Attendance, Workflow, Employee, messaging, database, or gateway boundary

Safe diagnostic steps​

  1. Record the affected operation, safe UTC window, response category, current status, client rendering, and safe correlation identifier.
  2. Choose the matching child page; compare direct and compatibility behavior only in an approved environment.

Resolution​

Follow the matching page. Avoid repeated state-changing requests until current state is confirmed.

Safe resolution​

Use only the resolution above and approved operational processes. Do not modify databases, replay messages, bypass authorization, or repeat ambiguous state-changing actions.

Validation​

Re-run the minimum safe read or approved synthetic test and confirm the expected state without exposing personal data.

Evidence to collect​

Collect the safe UTC window, route/operation category, response/status category, deployed version, affected scope count, and a correlation identifier. Exclude credentials, tokens, personal Leave details, employee identifiers, payloads, configuration values, and private topology.

Escalation​

Escalate to the owner of the classified boundary and the Leave owner when ownership is ambiguous.

Source References​

  • microservices/src/leave-service/Program.cs
  • microservices/src/leave-service/Application/LeaveWorkflows.cs
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx

See Also​

Keywords​

  • Leave troubleshooting
  • Leave Troubleshooting
  • Safe diagnostics

Revision Information​

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