Skip to main content

Gateway and Compatibility

Summary​

A route is unavailable or direct and compatibility behavior differs.

Audience​

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

Symptoms​

  • A route is unavailable or direct and compatibility behavior differs.

Scope​

Gateway routing, direct service surface, and monolith compatibility surface.

Likely causes​

Routing ownership mismatch, unavailable target, contract/parity drift, stale client assumption, or incomplete cutover.

Cause​

The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.

Safe diagnostic steps​

  1. Record route category and response; use approved smoke/parity tooling in a safe environment; compare sanitized status/shape/side effects without production mutation.
  2. Preserve tenant isolation and redact personal or security-sensitive data.
  3. Do not use direct database changes, authorization bypasses, or ad hoc broker operations.

Safe resolution​

Restore the approved route or rollback within the documented cutover boundary. Contract changes require owning-team review.

Resolution​

Apply only the Safe resolution described above and remain within the documented ownership boundary.

Validation​

Repeat parity and smoke checks; verify client behavior through the gateway.

Evidence to collect​

Route category, target surface, versions, timestamps, sanitized parity output, correlation identifiers.

Escalation​

Gateway owner plus Attendance/monolith compatibility owners; product owner for behavioral ambiguity.

Source References​

  • microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs
  • microservices/src/attendance-service/Api/AttendanceDirectEndpoints.cs
  • microservices/scripts/compare-attendance-shift-parity.ps1

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Gateway and Compatibility

Revision Information​

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