Skip to main content

Shift and Policy Resolution

Summary

Attendance cannot resolve a shift/policy or resolves an unexpected one.

Audience

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

Symptoms

  • Attendance cannot resolve a shift/policy or resolves an unexpected one.

Scope

Effective Shift, Attendance policy, and employee-profile fallback.

Likely causes

No effective active assignment, overlapping/invalid dates, no active tenant default, inactive configuration, or fallback profile mismatch.

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 effective date, active/default flags, assignments through supported APIs, and sanitized resolver evidence. Shift assignment has no confirmed UI.
  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 Time Office configuration through approved APIs/UI; never insert or edit rows directly.

Resolution

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

Validation

Re-query effective context for the same employee/date and recalculate through the supported workflow.

Evidence to collect

Sanitized employee/date, shift/policy references, effective ranges, response category, correlation identifier.

Escalation

Time Office/product owner, then Attendance owner if resolution remains inconsistent.

Source References

  • microservices/src/attendance-service/Application/Services/AttendancePolicyResolver.cs
  • microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs

See Also

Keywords

  • Attendance
  • Troubleshooting
  • Shift and Policy Resolution

Revision Information

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