Attendance Outbox Operations

Summary

Attendance outbox states describe publication progress, not end-to-end consumer completion.

Audience

• Support engineers, messaging owners, developers, and DevOps/SRE

Operating model

Pending rows await publication; failed rows remain eligible with attempt/error context; processed rows record successful publisher completion. The hosted relay periodically selects a bounded oldest-first batch and invokes the shared publisher.

Investigate backlog by confirming relay process health, broker availability signals, oldest pending age, retry growth, recurring event types and sanitized errors. Then verify consumer-owned ledgers/projections separately. Do not assume processed means consumed.

No Attendance-specific terminal retry cap, dead-letter store, replay endpoint, alert threshold or dashboard is confirmed. Replay is restricted and requires Attendance/messaging/data-owner approval, idempotency analysis and consumer coordination. No replay commands are documented.

Source References

• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs

Related Articles

• Attendance operations
• Attendance troubleshooting
• Attendance technical documentation

See Also

• Attendance database documentation
• Attendance events documentation

Keywords

• Attendance operations
• Support
• Reliability

Revision Information

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