Skip to main content

Requisition Workflow Troubleshooting

Symptoms​

Submission fails, direct decision is blocked, callback does not produce a terminal state, or opening creation is missing.

Scope​

Native requisition commands, optional Workflow HTTP integration, callback, and opening creation.

Cause​

Likely causes​

  • Requisition state is invalid.
  • Workflow-managed mode blocks local decision.
  • Workflow start/query failed.
  • Callback was absent/failed or state is already terminal.

Safe diagnostic steps​

  1. Confirm requisition and Workflow-mode status through supported reads.
  2. Locate safe workflow/correlation references.
  3. Confirm Workflow terminal outcome and callback receipt with the Workflow owner.
  4. Check whether an opening already exists before considering duplicate behavior.

Resolution​

Safe resolution​

Have owning services restore delivery or reconcile through an approved procedure. Do not fabricate callback requests or edit states.

Validation​

Verify one terminal requisition outcome and at most one corresponding opening.

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 start/query to Workflow owner, callback/command to Recruitment owner, and trust concerns to Identity/security.

Source References​

  • microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs
  • microservices/src/recruitment-service/Application/WorkflowIntegration.cs
  • microservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.cs
  • microservices/src/recruitment-service/Api/RecruitmentEndpoints.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