Skip to main content

Punch Processing

Summary​

Punch-in/out or manual punch entry fails, or history does not update.

Audience​

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

Symptoms​

  • Punch-in/out or manual punch entry fails, or history does not update.

Scope​

Self punch and punch-history workflows.

Likely causes​

Missing self permission/profile, invalid timestamp/order/state, weekly-off context, network failure, or compatibility routing failure.

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. Confirm employee context, current punch state, timestamp/date, weekly-off indication, route response, 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​

Retry only after transient connectivity recovers; correct valid input or use the governed reopen path. Dedicated missing/duplicate correction UI is not implemented.

Resolution​

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

Validation​

Reload today/history and verify the expected punch and derived Attendance state.

Evidence to collect​

Sanitized date/time category, action type, response category, correlation identifier.

Escalation​

Attendance owner; Gateway owner if direct/compatibility results differ.

Source References​

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

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Punch Processing

Revision Information​

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