Expense Outbox Operations

Summary

Pending and Failed records are eligible for oldest-first relay polling. Successful publication marks Processed; failure increments retry evidence. Consumption remains a separate downstream concern.

Backlog visibility exists through a foundation API, but payload exposure must be avoided. There is no retry ceiling, dead-letter flow, quarantine, or approved replay command. Operators must not alter rows or republish payloads manually.

Requires confirmation

Backlog thresholds, relay ownership, retention, monitoring, dead-letter design, replay authorization, and incident severity require confirmation.

Source References

• microservices/src/expense-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/expense-service/Messaging/OutboxRelayHostedService.cs
• microservices/src/expense-service/Api/ExpenseEndpoints.cs

Related Articles

• Expense operations documentation
• Expense troubleshooting
• Expense technical documentation

See Also

• Expense events
• Expense module

Keywords

• Expense operations
• Outbox Operations

Revision Information

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