> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/self-hosted/enterprise/deployment-manager/setting-up/setup-maintenance-windows.md). # Setup Maintenance Windows Schedule maintenance windows so deploy-affecting configuration changes apply only at agreed-upon times. Maintenance windows let you control when deploy-affecting configuration changes take effect on a device. Changes to services, streams, Workflows, and versions saved outside a window are queued for the next window. On production devices in Workspaces with configuration approval enabled, changes also need approval; a maintenance window does not approve them. By default, devices have no maintenance windows. Changes are released once any required approval is complete, then applied when the device receives them. #### Set up a Maintenance Window To set up a maintenance window, go to a specific device's dashboard in Deployment Manager. Go to the options menu on the top right and click on "Maintenance Window". Then: 1. Turn off "Apply Updates Immediately". 2. Choose the device's local "Timezone". This is the same timezone as the device settings, and Deployment Manager also sets the device's system timezone to it. 3. Check each day when updates can safely be applied and set its start and end times. To use one time range for every checked day, turn on "Use same time for all days". 4. Click "Save Configuration".
Maintenance Window Configuration dialog with Apply Updates Immediately off and Sunday and Saturday windows from 12:00 AM to 1:00 AM
#### Reboot the Device Each Maintenance Window To reboot the device once per maintenance window, check "Reboot device once per maintenance window" in the maintenance window settings. The device reboots a single time when a window opens, then will not reboot again until the next window. This option is only available when a maintenance window is set, not when applying updates immediately. #### Saving Changes Outside a Maintenance Window When you save configuration changes outside a maintenance window, deploy-affecting fields (services, streams, version changes, Workflow config) are deferred automatically. The configuration editor shows the effective config: your active config merged with any pending changes. It includes queued settings, so it does not confirm what the device is running. The following fields do not wait for a maintenance window, though configuration approval can still hold the save: * Maintenance window settings * Timezone * Device name and device type #### Pending Updates When changes are queued, a banner appears at the top of the Configuration and Service tabs showing that pending updates exist along with the scheduled apply time. To apply all pending changes immediately, click "Force Update Now" on the banner. This releases approved pending changes; it does not bypass configuration approval. Check reported service versions and stream output to verify application on the device. Approved pending changes are also released if you disable maintenance windows while changes are still queued. #### Operational Commands Restart and reboot commands run when the device receives them, regardless of maintenance windows. Configuration changes for running scripts or live camera tuning can still require production approval. These actions do not release unrelated pending updates. #### Automatic Updates Automatic version updates (when enabled for a service) respect maintenance windows. If the scheduled apply time has passed but the device is currently outside its maintenance window, the update waits until the device re-enters the window. Roboflow checks for automatic updates every hour. A device with no maintenance windows updates at the next check after a new version is available.