Skip to main content

Recruitment Troubleshooting Decision Tree

Symptoms​

Start with the closest symptom branch in the decision tree.

Scope​

The tree classifies Recruitment UI, service, dependency, persistence, messaging, and gateway symptoms; it does not authorize recovery actions.

Cause​

Likely causes​

Likely causes are summarized at each branch and detailed on the linked scenario pages.

Safe diagnostic steps​

  1. Choose the primary symptom.
  2. Follow the corresponding evidence branch.
  3. Open the detailed scenario page before taking any action.
  4. Escalate when ownership or resolution is not confirmed.

Resolution​

Safe resolution​

Use only the non-destructive resolution on the detailed page and the approved owning team.

Validation​

Verify the expected state through supported reads and sanitized evidence.

Evidence to collect​

Collect only time window, environment category, operation, status category, safe record/correlation reference, dependency category, and approved change context.

Escalation​

Use Support and escalation for the classified boundary.

Safe-use rule​

Follow the linked scenario page, stop before any destructive action, and escalate when ownership or recovery is not source-backed. Never collect tokens, candidate data, document contents, interview notes, offer/compensation values, credentials, secrets, internal addresses, or broker details.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/App.tsx
  • docs/modules/recruitment/operations/support-and-escalation.md

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