Event Delivery
Summary
Attendance changed but a downstream system does not reflect it.
Audience
Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.
Symptoms
- Attendance changed but a downstream system does not reflect it.
Scope
Transactional outbox publication and downstream consumption boundary.
Likely causes
Pending/failed outbox item, relay or broker unavailability, consumer failure, or expectation of an event not guaranteed by the documented contract.
Cause
The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.
Safe diagnostic steps
- Confirm the Attendance transaction, outbox status category, relay/broker health signals, documented event contract, and consumer telemetry using correlation/message references.
- Preserve tenant isolation and redact personal or security-sensitive data.
- Do not use direct database changes, authorization bypasses, or ad hoc broker operations.
Safe resolution
Restore the failed dependency and allow configured relay retries. Replay requires owner-approved tooling; no public replay command is documented.
Resolution
Apply only the Safe resolution described above and remain within the documented ownership boundary.
Validation
Verify publication and separately verify consumer processing; publication alone is insufficient.
Evidence to collect
Event type, aggregate reference, timestamps, outbox status, correlation/message reference, sanitized publisher/consumer logs.
Escalation
Attendance owner, messaging owner, then downstream consumer owner.
Related docs
Related Articles
Source References
microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
See Also
Keywords
- Attendance
- Troubleshooting
- Event Delivery
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly