Skip to main content

Attendance Capture

Summary​

Manual Attendance cannot be saved or submitted.

Audience​

Employees or administrators affected by the scenario, first-line support, QA, service owners, and operations.

Symptoms​

  • Manual Attendance cannot be saved or submitted.

Scope​

Manual daily capture from the weekly board.

Likely causes​

Missing context, invalid date/hours/status, inactive employee, resolved weekly off, duplicate daily outcome, permission failure, or invalid workflow state.

Cause​

The confirmed cause categories are listed under Likely causes above; determine the applicable category from sanitized evidence before taking action.

Safe diagnostic steps​

  1. Review the visible field validation, target employee/date, resolved weekly-off state, current daily record, response category, and correlation identifier.
  2. Preserve tenant isolation and redact personal or security-sensitive data.
  3. Do not use direct database changes, authorization bypasses, or ad hoc broker operations.

Safe resolution​

Correct the input or use the supported punch/reopen workflow. Do not override weekly-off or duplicate constraints through direct data changes.

Resolution​

Apply only the Safe resolution described above and remain within the documented ownership boundary.

Validation​

Reload the week and confirm the intended record/state and audit outcome.

Evidence to collect​

Sanitized employee/date, selected mode, response category, correlation identifier, and screenshot without personal data.

Escalation​

Attendance owner; Time Office owner when resolved calendar context is disputed.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/AttendanceStatus.tsx

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Attendance Capture

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly