Workflow Boundaries
Summary
Verified Recruitment workflow integration is HTTP request/callback behavior for requisition approval. It is not an onboarding/offboarding message subscription.
Audience
Workflow and Recruitment developers, integration engineers, QA, support, and architects.
Reference Content
The feature can be disabled, in which case a null implementation is used. Recruitment may verify workflow state before applying a callback. These behaviors relate to requisition approval before onboarding.
No Workflow consumer for OfferAccepted, CandidateOnboarded, CandidateJoined, EmployeeCreated or exit was found. No Workflow-produced lifecycle integration contract is part of this flow.
HTTP callback retry, authentication and duplicate-decision behavior belong to the API/workflow boundary and must not be described as broker retry or event idempotency.
Requires confirmation
Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/recruitment-service/Application/Commands/RequisitionCommands.csmicroservices/src/recruitment-service/Api/RecruitmentEndpoints.csmicroservices/src/workflow-service/Program.cs
Related Articles
See Also
Keywords
- Onboarding events
- Offboarding events
- Integration contracts
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly