Skip to main content

Submission and Approval

Summary​

Submit, approve, reject, or bulk review fails.

Audience​

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

Symptoms​

  • Submit, approve, reject, or bulk review fails.

Scope​

Attendance review workflow.

Likely causes​

Invalid current state, missing approver scope, invalid reason/input, stale board data, recalculation failure, or dependency/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. Reload the record, confirm current state and action scope, inspect the safe response category and correlation identifier, and retry items individually when a bulk result is ambiguous.
  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​

Use only an allowed transition with authorized scope and valid inputs; refresh stale UI state.

Resolution​

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

Validation​

Verify the new state, recalculated outcome on approval, and audit visibility.

Evidence to collect​

Record identifiers, attempted transition, bulk/single context, response categories, correlation identifiers.

Escalation​

Attendance owner; Identity owner for scope; Time Office owner if recalculation context fails.

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
  • Submission and Approval

Revision Information​

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