Transactional Outbox

Summary

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

Audience

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

Reference Content

The Attendance DbContext captures supported Attendance domain events before the same SaveChanges operation persists both aggregate changes and outbox rows. A hosted service waits, then processes batches at a fixed polling interval. Pending and previously failed rows are eligible, ordered by occurrence time.

Outbox rows include event and row identifiers, event type, JSON payload, occurrence and processing times, status, retry count, error summary, correlation identifier, optional tenant identifier, and source service. Scheduling mutations create no mapped outbox row.

Source References

• microservices/src/shared-kernel/Outbox/OutboxMessage.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/attendance-service/Infrastructure/Persistence.cs
• microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.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