Attendance Cutover and Rollback
Summary
Attendance and Time Office cutover must be capability-scoped; current tooling explicitly supports staged direct/shadow and compatibility ownership.
Audience
- Release approvers, Gateway/Attendance owners, migration engineers, QA, database owners, and architects
Safe lifecycle
Prepare approved builds/configuration; establish backups and rollback ownership; run dry-run/backfill and reconciliation; prove parity and smoke coverage; validate direct/shadow behavior; obtain go/no-go approval; change only the intended gateway capability; observe health, errors, outbox and dependent Payroll/UI flows.
Rollback returns routing/application ownership to the prior path when agreed criteria are met. It does not automatically reverse writes already accepted by Attendance. Reconcile writes created during the cutover window before resuming. Schema rollback or data deletion is outside this guide.
Required approvals include Attendance/Time Office product and service owners, Gateway, QA/release, database/migration and affected Payroll/support owners. Full daily-Attendance cutover automation remains Requires confirmation.
Source References
microservices/docs/attendance-shift-cutover-runbook.mdmicroservices/scripts/attendance-shift-cutover-go-no-go.ps1microservices/scripts/compare-attendance-shift-parity.ps1microservices/scripts/smoke-attendance.ps1
Related Articles
See Also
Keywords
- Attendance operations
- Support
- Reliability
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly