Attendance Known Limitations

Summary

This register consolidates limitations confirmed by current source without exposing exploitable internal detail.

Developers, architects, QA, DevOps, security, and support engineers.

Area	Confirmed limitation or maturity
Leave and holidays	No direct client or calculator input; precedence and synchronization remain transitional.
Punch processing	Complete duplicate, ordering, multi-interval, break, and correction rules are not implemented or confirmed.
Device/import	Biometric/device ingestion and file import are not implemented.
Employee profile	Explicit local projection exists without confirmed event synchronization or freshness control.
Policy/scheduling	No employee-specific policy assignment, policy effective dates, rotating roster, or break model.
Calculation	Only worked-hours policy rules drive status; business rounding and some period-change behavior require confirmation.
Payroll lock	Explicit guard is limited to reopen approval; dependency availability/reconciliation behavior requires internal review.
Health/metrics	Health is process-only; dependency checks and application metrics are absent.
Performance	No cache, pagination across all list queries, benchmark, or performance guarantee.
Gateway	Attendance and Time Office ownership remain independently transitional.
Testing	Script coverage exists, but no Attendance-specific .NET test project was found.
Messaging	No confirmed dead-letter workflow, retry ceiling, ordering guarantee, or inbound consumer.

These are source observations, not delivery commitments or vulnerability disclosures.

microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
microservices/src/attendance-service/Application/Services/PunchWorkflow.cs
microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
microservices/src/attendance-service/Program.cs
microservices/src/gateway-api/Program.cs