Skip to main content

Weekly Off Behavior

Summary​

Manual capture is blocked or a punch on a weekly off produces an unexpected result.

Audience​

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

Symptoms​

  • Manual capture is blocked or a punch on a weekly off produces an unexpected result.

Scope​

Attendance-owned weekly-off rules.

Likely causes​

Configured weekday is a weekly off, stale UI/configuration, compatibility mismatch, or an expectation involving Leave/holiday precedence that requires confirmation.

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 the configured active weekday, target date, UI indication, route surface, 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 weekly-off configuration through its supported page; use punch workflow for actual work where policy permits. Do not assume Leave/holiday precedence.

Resolution​

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

Validation​

Reload configuration and Attendance for the date on the intended route surface.

Evidence to collect​

Date, configured weekdays, route surface, response category, correlation identifier.

Escalation​

Time Office/product owner; Gateway owner for parity; Attendance owner for enforcement.

Source References​

  • microservices/src/attendance-service/Application/Services/AttendanceCommands.cs
  • microservices/src/attendance-service/Application/Compatibility/ShiftPolicyCompatService.cs

See Also​

Keywords​

  • Attendance
  • Troubleshooting
  • Weekly Off Behavior

Revision Information​

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