Skip to main content

Reopening

Summary​

A reopen request cannot be created, approved, or rejected.

Audience​

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

Symptoms​

  • A reopen request cannot be created, approved, or rejected.

Scope​

Reopen creation and decision.

Likely causes​

Future date, existing pending request, invalid state/scope, Payroll-locked period, missing record/context, or Payroll dependency 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 date, pending-request presence, current state, requester/approver scope, Payroll-lock result 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​

Use the existing pending request, correct the date/reason, or wait for/coordinate the governed Payroll process. Do not bypass a lock.

Resolution​

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

Validation​

Reload requests and the Attendance record; confirm decision and recalculation/audit result.

Evidence to collect​

Request/record reference, date, action, lock-result category, response category, correlation identifier.

Escalation​

Attendance owner; Payroll owner for lock/freeze; Identity owner for scope.

Source References​

  • microservices/src/attendance-service/Application/Services/ReopenRequestWorkflow.cs
  • microservices/src/attendance-service/Infrastructure/PayrollLockClient.cs

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Reopening

Revision Information​

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