Correlation and Causation

Summary

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

Audience

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

Reference Content

Attendance mapping creates a correlation value from the numeric tenant reference, worker reference, and attendance date. Event identifiers are generated independently. Causation, cross-service tenant, and user envelope values are set to null by the mapper.

The serialized contract retains correlation and causation fields. The persisted outbox retains correlation but not causation or user. Relay metadata includes correlation but omits causation and schema version. The Integration consumer reads correlation from message properties or metadata and falls back to the event identifier when computing its effective correlation.

This supports limited tracing of adjacent Attendance lifecycle messages. It does not correlate scheduling configuration changes, and reuse of the date-based value means it is not a unique request identifier.

Source References

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