Performance Outbox Troubleshooting
Symptoms
Expected outbox intent is absent, remains pending/failed, or downstream effects do not appear.
Scope
Domain mapping, local transaction, relay publication, and consumer boundary.
Cause
Likely causes
Action has no event; transaction failed; mapping gap; publisher unavailable; repeated relay failure; no/failed consumer.
Safe diagnostic steps
- Confirm the action should emit an event.\n2. Check sanitized outbox identity/type/status/time category.\n3. Check relay warning and publication outcome category.\n4. Check consumer evidence separately.
Resolution
Safe resolution
Allow implemented retry behavior and escalate the failing boundary. Do not modify outbox data or issue replay/broker operations.
Validation
Confirm status progression and independent consumer completion evidence.
Evidence to collect
Collect only environment category, time window, capability/route, status or error category, sanitized correlation reference, lifecycle state category, and recent approved change context.
Escalation
Escalate mapping/row absence to Performance; publication to messaging; consumer completion to Notification.
Related documentation
Source References
microservices/src/performance-service/Infrastructure/PerformanceDbContext.csmicroservices/src/performance-service/Messaging/OutboxRelayHostedService.csmicroservices/src/shared-kernel/Messaging/OutboxProcessor.cs
Summary
This Draft page provides non-destructive, source-backed diagnosis and explicitly stops where recovery authority is not confirmed.
Audience
Performance users, support, operations, engineering, QA, architecture, security, and implementation teams.
Overview
Use supported reads and sanitized evidence. Never expose personal/evaluation content, credentials, configuration values, infrastructure details, or operational commands.
Related Articles
See Also
Keywords
- Performance troubleshooting
- Safe diagnostics
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly