Event Consumers

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 Integration Service subscribes to AttendanceSubmitted, AttendanceApproved, and AttendanceRejected. It checks processed event identifiers, audits delivery stages, resolves configured downstream targets, retries target delivery, and persists exhausted failures.

Consumer category	Verified result
Native scheduling	None
Compatibility	None
Gateway	None; HTTP routing only
Notification	No attendance or scheduling type in the resolver binding list
Integration orchestrator	Three adjacent attendance types
External	No source-backed consumer found

No consumer for AttendancePunched or AttendanceReopened was found. Runtime deployment of configured downstream targets requires confirmation.

Source References

• microservices/src/integration-service/Messaging/IntegrationEventConsumer.cs
• microservices/src/integration-service/Domain/IntegrationEntities.cs
• microservices/src/integration-service/Orchestration/EventDispatcher.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/gateway-api/Program.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