THE FIELD GUIDE / PATCHING
Schedules, windows & rollouts
Timezone-aware patching with canaries, urgency rules and recovery gates.
Build a schedule
Open Patch schedules and choose daily, weekly or monthly recurrence. Select an IANA timezone, start time, allowed start-window length, regular priorities and server scope. All-server schedules can include future enrollments. The month calendar and hourly view show scheduled windows and urgent runs.
Handle urgent work
High and critical out-of-cycle rules each have a delay from first discovery. They respect server maintenance windows unless an administrator explicitly approves a bypass for that priority. Detection follows repository refresh cadence.
Roll out in stages
Create an ordered rollout with a canary first. Exact-version jobs and dependency gates keep later hosts waiting until the earlier stage passes. Review the reboot and snapshot policy for every host. Failed or interrupted stages block later work.
When a window closes
Windows gate job start; running installation and recovery can extend beyond the window. Offline or unhealthy targets wait within the allowed start window. Missed windows are skipped. Pausing or editing a schedule cancels queued work; an already running patch can finish.
Open the application reference for capability scope and technical details.
Open Open PATCH_SCHEDULES.md on GitHub ↗