Leave Outbox Operations

Summary

Leave stores integration messages transactionally and a hosted relay polls eligible records for publication with retry behavior.

Audience

Support, DevOps/SRE, messaging and Leave owners, QA, and architects.

Overview

Conceptual states include pending, failed/retry-eligible, and processed. Stored publication progress proves relay handling, not downstream consumption. Backlog review should use approved observability/data-access channels and aggregate evidence, not raw personal payloads.

Retry behavior is source-defined and bounded by relay/processor logic. A clear terminal-failure operating procedure, dedicated backlog metric, and public replay tool were not found. Manual replay commands and direct database status changes are prohibited by this guide.

Escalate relay errors to Leave and messaging owners; downstream absence after successful publication to the consumer owner; and persistent data-store errors to database/SRE owners.

Source References

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

Related Articles

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Outbox Operations
• Service support

Revision Information

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