Guide
Diagnose and retry domain event delivery
Trace a business change from its committed event to routing, consumer processing and the final receipt.
Demo baseline · November 13, 2026Find the event and consumer
Open Administration → Domain event delivery. Use Events and Coverage to identify the committed event and the registered topic. Use Consumers to check subscription state and history policy, then open Deliveries for the event and consumer. The domain event ledger tracks business changes. Use Event operations when investigating monitoring alerts.
Diagnose the stage
| Stage | Evidence to check |
|---|---|
| No committed event | Confirm the source mutation completed, the record identifier is correct, and the topic is registered. A rolled-back mutation leaves no committed event. |
| Event present, delivery missing | Check topic/consumer match, subscription state and history policy, then inspect routing state. |
| Delivery pending | Check the next attempt, consumer state and worker health. A current lease can indicate another worker is processing the delivery. |
| Delivery failed | Capture the error classification, attempts, relevant version and downstream dependency. Fix the cause before using Retry delivery with a reason. |
| Delivery complete | Verify the expected downstream effect. For a downstream queue, check its own receipt to confirm completion. |
Verify recovery
Check the original event and delivery after retry. Confirm the final state, attempt history and intended effect on the linked record or service. Completed delivery cannot be replayed through the retry action. Preserve the original identifiers and audit history.