Skip to main content

Troubleshoot Leave Event Delivery

Summary​

Safe triage for outbox backlog, publication failure, and missing downstream effects.

Audience​

Employees or administrators affected by the scenario, first-line support, QA, service owners, and architects.

Symptoms​

A Leave event remains pending/failed, or Payroll/Notification does not reflect a confirmed transition.

Scope​

Transactional outbox storage, relay publication, broker delivery, and downstream consumption.

Cause​

The cause must be confirmed from current state and source-backed evidence.

Likely causes​

  • Relay or broker unavailable
  • Message remains retry-eligible/failed
  • Publication succeeded but consumer failed or is delayed
  • Consumer has no contract coverage for that event

Safe diagnostic steps​

  1. Confirm the Leave transaction and outbox state through approved evidence.
  2. Separate publication evidence from consumer completion.
  3. Review aggregate backlog/failure signals and safe correlations, not payloads.

Resolution​

Restore the failing owned component and use only approved replay/reconciliation processes. No replay command or direct status edit is authorized.

Safe resolution​

Use only the resolution above and approved operational processes. Do not modify databases, replay messages, bypass authorization, or repeat ambiguous state-changing actions.

Validation​

Confirm processed publication and the expected consumer projection once, accounting for eventual delivery.

Evidence to collect​

Collect the safe UTC window, route/operation category, response/status category, deployed version, affected scope count, and a correlation identifier. Exclude credentials, tokens, personal Leave details, employee identifiers, payloads, configuration values, and private topology.

Escalation​

Leave/messaging owner for relay; Payroll or Notification owner for consumption; SRE for platform outage.

Source References​

  • microservices/src/leave-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/leave-service/Infrastructure/LeaveDbContext.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

See Also​

Keywords​

  • Leave troubleshooting
  • Troubleshoot Leave Event Delivery
  • Safe diagnostics

Revision Information​

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