Skip to main content

Leave Troubleshooting Decision Tree

Summary​

Non-destructive decision tree for classifying common Leave incidents.

Audience​

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

Symptoms​

The affected Leave boundary is not yet known.

Scope​

Initial classification across UI, application, dependency, data, messaging, and routing concerns.

Cause​

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

Likely causes​

  • Access/context
  • Business validation/state
  • Dependency/integration
  • Persistence/migration
  • Gateway/compatibility

Safe diagnostic steps​

  1. Start at the reported symptom and follow only read-only evidence checks.
  2. Open the linked scenario page before any retry or recovery action.

Resolution​

Use the owner-approved resolution on the matching troubleshooting page.

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​

Confirm the chosen scenario matches the observed boundary before proceeding.

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​

Leave owner coordinates when more than one boundary remains plausible.

Source References​

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

See Also​

Keywords​

  • Leave troubleshooting
  • Leave Troubleshooting Decision Tree
  • Safe diagnostics

Revision Information​

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