Skip to main content

Gateway and Compatibility Troubleshooting

Symptoms​

Route is unreachable, compatibility response differs, redirect is unexpected, or native/compatibility state appears inconsistent.

Scope​

Gateway routing, client redirects, compatibility mappings, and shared storage.

Cause​

Likely causes​

  • Gateway route ownership/configuration mismatch.
  • Client legacy route intentionally redirects.
  • Compatibility label/identifier mapping differs from native shape.
  • No full parity comparator/cutover tooling exists.

Safe diagnostic steps​

  1. Identify public, protected, native, or compatibility route category.
  2. Confirm client redirect behavior from source.
  3. Compare sanitized supported reads for the same synthetic record.
  4. Collect gateway/service correlation evidence without internal addresses.

Resolution​

Safe resolution​

Have Gateway or Recruitment owners correct approved routing/mapping. Use rollback only through an approved cutover plan.

Validation​

Verify route reachability and semantically consistent state across intended surfaces.

Evidence to collect​

Collect the time window, environment category, affected operation, expected/actual status category, safe record reference, correlation reference where available, dependency/error category, and recent approved change. Exclude personal data, resumes/documents, interview notes, tokens, offer/compensation values, credentials, bank/KYC data, secrets, and configuration values.

Escalation​

Escalate routing to Gateway/DevOps, mapping to Recruitment, UI redirects to frontend, and parity/cutover to architecture.

Source References​

  • microservices/src/gateway-api/appsettings.json
  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatMapper.cs
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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