Skip to main content

Employee Event Retry and Failure Handling

Summary​

The shared publisher records failed outbox attempts, while inspected direct consumers negatively acknowledge and requeue processing failures. Employee-specific terminal failure handling is not implemented.

Audience​

  • Developers, QA engineers, DevOps engineers, and support engineers

Overview​

If the shared event bus is unavailable or publication throws, OutboxProcessor increments the message retry count and asks the Employee store to mark it failed. The store includes failed messages in later pending reads. Because no Employee relay invocation is confirmed, the schedule and operational trigger for another attempt Require confirmation.

Failure flow​

Confirmed controls and gaps​

ConcernEvidence status
Publisher failure recordedConfirmed
Failed Employee outbox message eligible againConfirmed
Direct consumer failure requeuedConfirmed for Leave, Payroll, and Document consumers
Employee retry ceiling/backoffNot implemented in the Employee store/processor path
Employee dead-letter transitionNot implemented
Integration Service failed-event/dead-letter modelConfirmed for that service, not the Employee outbox
Alert thresholds and incident ownershipRequires confirmation
Replay authorization and runbookRequires confirmation

Safe operational guidance​

Operators should use approved observability and service procedures to confirm whether messages progress; this documentation does not prescribe production data edits or expose topology. Repeated failures should be investigated for contract compatibility and consumer availability without copying raw payloads into tickets or logs.

Source References​

  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/src/shared-kernel/Messaging/RabbitMqEventBus.cs
  • microservices/src/employee-service/Infrastructure/Persistence.cs
  • microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
  • microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
  • microservices/src/document-service/Messaging/DocumentReadModelConsumer.cs
  • microservices/src/integration-service/Domain/IntegrationEntities.cs

See Also​

Keywords​

  • Retry behavior
  • Consumer requeue
  • Failed outbox

Revision Information​

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