Leave Operations
Summary
Leave operations cover service startup, persistence migration, process health, telemetry, background messaging, employee projection, Attendance and Workflow dependencies, gateway ownership, reconciliation, and support.
Audience
DevOps/SRE, support engineers, developers, QA, architects, product owners, and implementation partners.
Overview
The Leave Service is an extracted runtime with tenant-scoped Leave responsibilities, but monolith compatibility and gateway routing remain Transitional. Process health alone does not prove database, broker, Attendance, Workflow, employee-projection, or outbox readiness.
Use non-destructive observation and approved deployment controls. Never repair production data directly from these pages.
Documentation map
- Operational overview
- Configuration reference
- Deployment and startup
- Health and observability
- Smoke testing
- Workflow dependency
- Attendance dependency
- Employee projection
- Outbox
- Consistency and reconciliation
- Cutover and rollback
- Support and escalation
- Operational checklist
Source References
microservices/src/leave-service/Program.csmicroservices/src/leave-service/Messaging/OutboxRelayHostedService.csmicroservices/src/leave-service/Messaging/EmployeeProfileConsumer.cs
Related Articles
See Also
Keywords
- Leave operations
- Leave Operations
- Service support
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly