Leave Known Limitations

Summary

Leave remains transitional across policy enforcement, UI coverage, authorization parity, ownership, operations, integration guarantees, and testing.

Product owners, architects, developers, QA, support, DevOps/SRE, and implementation partners.

Stored notice, duration, annual-cap, type-active, half-day, negative-balance, and carry-forward governance is not fully enforced.
Request edit/resubmit and reserved Pending balance are not implemented.
Carry forward and encashment have storage/domain foundations but no complete workflows, scheduling, UI, or confirmed Payroll handoff.
No current UI manages extracted Leave types/policies or displays Workflow state/timeline.
ESS error presentation and broader accessibility evidence are incomplete; no WCAG claim exists.
Monolith, compatibility, gateway, and Leave Service ownership can diverge.
Extracted-service authorization/team-scope parity requires confirmation.
Leave/Attendance/legacy payroll calendar ownership and precedence remain transitional.
Health is process-only; readiness/liveness, dependency probes, dedicated metrics, consumer lag, and backlog alerting are absent.
Outbox publication does not prove consumption; no public replay/reconciliation procedure exists.
Employee deletion propagation and general inbox/reconciliation tooling are not confirmed.
Notification coverage is incomplete; Payroll classification/parity has confirmed caveats.
No formal Leave-specific .NET test project or dedicated Leave frontend test was found.
Local persistence and external integrations are not a distributed transaction.
A Leave-specific cutover/go-no-go runbook was not found.