Event Ordering

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 Attendance outbox store selects eligible rows by occurrence time and the processor publishes the returned batch sequentially. This is local best-effort ordering only.

No verified implementation provides:

• a stable tie-breaker for equal occurrence timestamps;
• per-worker, per-tenant, or per-aggregate partition ordering;
• a monotonic sequence number;
• consumer-side reordering or stale-event rejection;
• ordering across service instances or concurrent relays;
• scheduling-event ordering, because scheduling events do not exist.

Consumers must not interpret occurrence-time sorting as a global or causal ordering guarantee.

Source References

• microservices/src/attendance-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/contracts/Events/IntegrationEvent.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