Attendance Known Limitations

Summary

These limitations consolidate confirmed gaps across the Attendance documentation set.

Product owners, architects, engineering, QA, support, and operations.

Service health is process-only; dependency readiness/liveness probes are not implemented.
Dedicated Attendance business metrics and an operational outbox dashboard are not implemented.
Outbox delivery does not prove downstream consumption; a documented terminal-failure/replay workflow is not implemented.
Granular authorization parity between monolith and extracted service is transitional.
Gateway direct/compatibility ownership remains transitional.
No employee shift-assignment administration screen is confirmed.
Attendance policy rule editing is not exposed in the confirmed UI.
Device/biometric ingestion and import UI are not implemented in the confirmed Attendance screens.
Missing/duplicate punch correction has no dedicated confirmed UI.
Responsive and accessibility compliance requires confirmation; no WCAG claim is supported.
Frontend automated test coverage for the confirmed Attendance screens was not found.
Leave/holiday/weekly-off precedence, rotating rosters, rounding policy, snapshot replacement governance, and post-Payroll correction procedures require confirmation.
Employee-profile synchronization across coexistence boundaries remains a documented operational gap.

The source-backed catalog above is the normative reference content for this Draft page.

microservices/src/attendance-service/Program.cs
microservices/src/attendance-service/Infrastructure/OutboxRelayHostedService.cs
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx