Skip to main content

Workflow Dependency Operations

Purpose​

Supports workflow-enabled requisition submission and callback diagnosis.

Confirmed implementation​

Workflow is optional. When enabled, submission starts an HTTP workflow and persists an instance reference. A terminal callback applies a decision idempotently and avoids duplicate opening creation.

Safe operational guidance​

Confirm mode, submission state, safe workflow reference, Workflow outcome, callback receipt, and Recruitment terminal state through supported evidence. Do not fabricate callbacks.

Signals and evidence​

Start failure, absent instance reference, callback failure, duplicate terminal callback, or state mismatch.

Risks and escalation​

Callback authentication, replay protection, delivery ownership, reconciliation, and production escalation require confirmation.

Source References​

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