Leave Technical Known Limitations

Summary

Confirmed limitations span policy enforcement, incomplete foundations, ownership transition, runtime visibility, and test coverage.

Developers, architects, QA, DevOps, support, and product owners.

Request/approval does not enforce balance sufficiency or stored negative-balance governance.
Stored notice, duration, annual cap, carry-forward maximum, type activity, and half-day eligibility are not fully enforced.
Request edit/resubmit and reserved Pending balance are not implemented.
Carry forward and encashment lack application workflows, scheduling, UI, and Payroll handoff.
Leave/Attendance calendar ownership overlaps; Leave does not automatically mutate Attendance.
Workflow integration and gateway/monolith ownership remain Transitional.
Final extracted-service authorization parity requires confirmation.
Health is process-only; dependency readiness/liveness and dedicated metrics are absent.
No application cache, broad pagination, or explicit no-tracking query strategy exists.
No formal Leave-specific .NET test project was found.
Notification resolver covers approval/rejection, not all Leave events; monolith parity differs.
Payroll paid/unpaid classification uses a compatibility convention that differs from explicit Leave type metadata.
Employee deletion propagation and reconciliation tooling are not confirmed.
Local saves and external integrations do not form a distributed transaction.