Skip to main content

Retention and Cleanup

Audience​

Developers, database engineers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling persistence behavior and boundaries.

Summary​

No scheduling-specific retention policy, purge service, cleanup job, archive process, partition lifecycle, time-to-live configuration, or data-erasure workflow was found.

Retained state​

Canonical shifts are soft-deactivated so assignments and historical attendance can retain references. Weekly-off rules use active state rather than deletion during compatibility replacement. Assignments retain effective ranges and active state. Audit and timeline records are append-oriented.

Policy rule replacement can delete dependent rule rows through the owned cascade relationship. That is configuration replacement, not a time-based retention policy.

Gaps​

Retention periods for shifts, assignments, policies, rules, audit, timeline, backfill audit, and legacy calendar records require confirmation. Legal hold, privacy erasure, archival, backup retention, and recovery objectives were not established from source.

Classification​

Lifecycle retention is Partial. Formal governance and automated cleanup are Not implemented in the reviewed scheduling code.

Source References​

  • microservices/src/attendance-service/Domain/TimeOffice/Shift.cs
  • microservices/src/attendance-service/Domain/TimeOffice/EmployeeShiftAssignment.cs
  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs

See Also​

Keywords​

  • Workforce Scheduling database
  • Shift persistence
  • Attendance policy storage

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20