Leave Employee Projection Operations

Summary

Leave consumes confirmed Employee lifecycle events into a local EmployeeProfile projection and requeues failed consumption.

Audience

Support, DevOps/SRE, Employee/Leave integration owners, QA, and architects.

Overview

Missing/stale profile symptoms include inability to resolve employee context or outdated active/joining data. Collect safe event identity/time, tenant-safe correlation, consumer outcome, and projection freshness evidence.

Duplicate handling compares the last event identity and stale handling compares occurrence time. There is no general inbox ledger, confirmed deletion subscription, or documented reconciliation utility. Do not edit the projection directly; escalate to Employee integration and Leave owners.

Source References

• microservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
• microservices/src/leave-service/Domain/Leave/EmployeeProfile.cs
• microservices/src/contracts/Events/EmployeeCreatedEvent.cs

Related Articles

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Employee Projection Operations
• Service support

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly