Compatibility Event Behavior

Summary

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

Audience

Developers, migration engineers, QA engineers, support engineers, and solution architects.

Reference Content

Compatibility scheduling endpoints translate legacy-shaped requests into canonical Attendance Service writes. The command services persist audit and timeline records, but these records are not domain events, integration contracts, outbox messages, or replayable broker deliveries.

Path	Audit/timeline	Integration event
Native scheduling command	Verified	None
Compatibility scheduling command	Verified	None
Monolith scheduling workflow	Conventional persistence	None found
Backfill	Audit evidence	No scheduling event contract

Compatibility changes therefore remain synchronous and Transitional. Consumers cannot subscribe to legacy scheduling mutations through the verified event bus.

Source References

• microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
• microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs
• Controllers/ShiftsController.cs
• Services/ShiftService.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