Skip to main content

Recruitment Event Delivery Troubleshooting

Symptoms​

Outbox is Pending/Failed, an expected outbox row is absent, or no downstream effect appears after Processed.

Scope​

Domain mapping, transactional outbox, relay publication, and absent confirmed consumers.

Cause​

Likely causes​

  • Domain event is unmapped, notably offer withdrawal.
  • Relay publication failed and remains retry-eligible.
  • Message is Processed but no consumer exists.
  • Retry/dead-letter/replay governance is absent.

Safe diagnostic steps​

  1. Confirm business transaction and supported event mapping.
  2. Inspect outbox state/retry/correlation through supported read.
  3. Review relay logs for the safe correlation window.
  4. Distinguish publication from consumption and confirm consumer ownership.

Resolution​

Safe resolution​

Allow implemented retry behavior and escalate persistent failure. Do not replay, edit, or republish messages without an approved future procedure.

Validation​

Confirm expected state progression or document the unmapped/no-consumer outcome.

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 mapping/relay to Recruitment, transport to messaging/DevOps, and missing consumer to product/architecture.

Source References​

  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • docs/modules/recruitment/events/event-catalog.md

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