Skip to main content

Onboarding and Employee Provisioning Troubleshooting

Symptoms

Onboarding cannot start/progress/complete, Employee creation fails/duplicates, or Employee reference is missing.

Scope

Accepted-offer eligibility, onboarding lifecycle, synchronous Employee dependency, and persisted Employee reference.

Cause

Likely causes

  • Offer/onboarding state is ineligible.
  • Required employee/organization input is absent.
  • Employee Service failed or returned duplicate/conflict.
  • Cross-service persistence is inconsistent.

Safe diagnostic steps

  1. Confirm offer/onboarding status and safe references.
  2. Classify validation versus Employee dependency failure.
  3. Ask Employee owner to confirm outcome using safe reference.
  4. Check whether Employee reference persisted before any approved retry.

Resolution

Safe resolution

Correct source-required input or coordinate an owner-approved retry/reconciliation. Do not expose credentials/bank/KYC data or edit either database.

Validation

Confirm one Employee record/reference and Completed Recruitment state, or a recoverable non-terminal state.

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 to Recruitment and Employee owners; involve Identity for login gaps, organization owner for manager mapping, and privacy/security for sensitive data.

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
  • microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs

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