Recruitment Notification Integration Events
Summary
Notification Service has a generic event consumer, but its supported resolver/subscription list contains no Recruitment contract type.
Audience
Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.
Overview
None of the eleven Recruitment contracts is in the Notification resolver's supported event-type list, and no Recruitment case exists in its resolver. Therefore there is no confirmed Recruitment notification subscription, intent generation, template selection, recipient resolution, or delivery.
A published Recruitment event does not imply notification delivery. Notification retry behavior applies only after a supported subscription produces an intent; it is not Recruitment coverage. Templates, channels, delivery ownership, consent, and retry/reconciliation remain Not implemented for Recruitment events.
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/notification-service/Application/EventNotificationResolver.csmicroservices/src/notification-service/Messaging/NotificationEventConsumer.csmicroservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/contracts/Events/RecruitmentLifecycleEvents.cs
Related Articles
See Also
Keywords
- Recruitment events
- Notification Integration Events
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly