Skip to main content

Recruitment Troubleshooting

Summary​

Use these pages to classify Recruitment symptoms and collect non-destructive evidence. They do not authorize database edits, forged callbacks, message replay, token handling, infrastructure changes, or repeated business mutations.

Symptoms​

Any Recruitment access, workflow, opening, candidate, interview, offer, onboarding, document, notification, event, database, gateway, report, or bulk-operation symptom.

Scope​

Initial classification and routing to the detailed source-backed scenario pages.

Cause​

Likely causes​

The cause may be in the Recruitment UI/API/domain, tenant or identity context, a synchronous dependency, messaging, persistence, or gateway compatibility boundary.

Safe diagnostic steps​

  1. Select the scenario matching the primary symptom.
  2. Follow only its supported read and sanitized-evidence steps.
  3. Stop and escalate when the recovery action or ownership is not source-backed.

Resolution​

Safe resolution​

Use the detailed scenario page and owning team. Do not perform direct data repair, callback fabrication, token manipulation, event replay, or infrastructure mutation.

Validation​

Confirm the expected state through supported reads and safe correlation evidence.

Evidence to collect​

Collect the time window, environment category, operation, expected/actual status category, safe record reference, correlation reference, dependency category, and recent approved change. Exclude all personal, token, document, interview, credential, and compensation data.

Escalation​

Use the affected component owner and the support escalation model.

Scenario map​

When evidence is insufficient, classify the outcome as Requires confirmation and escalate to the owning boundary.

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

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