Delivery Guarantees

Summary

This page records the verified Workforce Scheduling event boundary and its adjacent Attendance integration behavior.

Audience

Developers, integration engineers, operators, QA engineers, and solution architects.

Reference Content

The verified design provides transactional capture for the five mapped Attendance events and durable broker messages. It does not prove exactly-once delivery. Publish and “mark processed” are separate operations, so a failure between them can cause redelivery. The publisher does not use a verified broker-confirm step, and mandatory routing is disabled; a successful publish call is not proof that a consumer received or processed the message.

The practical classification is at-least-once potential with gaps in end-to-end assurance, not a formal guarantee. Scheduling changes have no event delivery at all.

Source References

• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/shared-kernel/Messaging/RabbitMqEventBus.cs
• microservices/src/integration-service/Messaging/IntegrationEventConsumer.cs

Related Articles

• Events overview
• Event limitations
• Event source map

See Also

• Technical documentation
• API documentation
• Database documentation

Keywords

• Workforce Scheduling events
• Attendance integration contracts
• Transactional outbox

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20