Recruitment Workflow Integration Events

Summary

Recruitment Workflow integration uses synchronous HTTP and a terminal HTTP callback; no Workflow event subscription is registered.

Audience

Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.

Overview

A callback duplicate after terminal decision is acknowledged without creating another opening. Direct decisions are blocked while Workflow-managed. Requisition outcomes do not raise Recruitment domain events, so callbacks produce no Recruitment outbox contract.

Callback authentication/replay protection and separate HTTP failure ownership require confirmation. No Workflow integration event contract is inferred from the HTTP behavior.

Requires confirmation

Consumer ownership, tenant-envelope policy, correlation/causation policy, retry limits, replay, ordering, contract governance, reconciliation, monitoring, and production support require confirmation.

Source References

• microservices/src/recruitment-service/Application/WorkflowIntegration.cs
• microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs
• microservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.cs
• microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
• microservices/src/recruitment-service/Program.cs

Related Articles

• Recruitment events documentation
• Event catalog

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment events
• Workflow Integration Events

Revision Information

• Status: Draft
• Last reviewed: 2026-07-16
• Review cycle: Quarterly