Skip to main content

Troubleshoot Leave Gateway and Compatibility

Summary​

Safe triage for routing, compatibility parity, and direct-versus-legacy divergence.

Audience​

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

Symptoms​

Gateway Leave calls fail, direct and compatibility results differ, or the UI appears to use unexpected ownership.

Scope​

Gateway routing, direct Leave endpoints, compatibility endpoints, monolith coexistence, and client API dependencies.

Cause​

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

Likely causes​

  • Gateway route/ownership configuration mismatch
  • Target service unavailable
  • Compatibility contract differs from direct contract
  • Tenant/authentication context differs
  • Underlying stores diverged

Safe diagnostic steps​

  1. Record route class, response category, deployment version, and safe correlation.
  2. Compare an approved non-sensitive read through direct and compatibility paths.
  3. Confirm selected ownership without exposing routing-toggle names or private topology.

Resolution​

Restore approved routing/application ownership or invoke the approved rollback boundary. Reconcile data through owners; do not switch clients or edit stores ad hoc.

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 gateway and intended target produce contract-compatible results for the approved smoke case.

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​

Gateway owner, Leave/monolith owners, Identity/security, database, and release approver.

Source References​

  • microservices/src/gateway-api/Program.cs
  • microservices/src/leave-service/Api/LeaveEndpoints.cs
  • Controllers/LeaveRequestsController.cs
  • microservices/scripts/smoke-leave.ps1

See Also​

Keywords​

  • Leave troubleshooting
  • Troubleshoot Leave Gateway and Compatibility
  • Safe diagnostics

Revision Information​

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