Skip to main content

Recruitment Notification Troubleshooting

Symptoms​

A stakeholder expected a Recruitment notification but none is visible.

Scope​

Recruitment event production and the absent Notification resolver/subscription.

Cause​

Likely causes​

  • No Recruitment Notification mapping is implemented.
  • No confirmed Recruitment consumer/subscription exists.
  • Outbox publication is mistaken for notification delivery.

Safe diagnostic steps​

  1. Confirm source business state.
  2. Check Recruitment outbox publication state safely.
  3. Verify the inspected Notification resolver has no Recruitment mapping.
  4. Do not repeat the business operation merely to trigger a notification.

Resolution​

Safe resolution​

Use an approved alternate communication process if one exists and escalate the missing capability. Do not promise delivery.

Validation​

Confirm the business action remains correct and record notification capability as Not implemented/Requires confirmation.

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 to Recruitment product and Notification owners; architecture must define contract/ownership before implementation.

Source References​

  • microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.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