> 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/deploy/device-manager/setting-up/setup-maintenance-windows.md).

# Setup Maintenance Windows

Maintenance windows let you control when deploy-affecting configuration changes take effect on a device. When a maintenance window is configured, changes to services, streams, workflows, and versions are queued and applied only during the next scheduled window. This prevents disruptions to production inference outside of agreed-upon times.

By default, devices have no maintenance windows and all changes apply immediately.

#### 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 Windows".

You can then define maintenance windows for each device based on your operational needs. Choose specific days and times when updates can safely be applied.

Key options:

* **Timezone** - Set the device's local timezone for accurate scheduling
* **Per-day scheduling** - Configure different windows for each day of the week
* **Same time for all days** - Use a single schedule across multiple days

#### 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, which is your active config merged with any pending changes, so you always see what will be deployed at the next window.

The following fields always apply immediately, even outside a window, since they only affect scheduling and display:

* 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 merges the full pending queue into the active config right away.

Pending changes are also flushed automatically if you disable maintenance windows while changes are still queued.

#### Operational Commands

Restart, reboot, run script, and live camera tuning commands always apply immediately regardless of maintenance windows. These are intentional, user-initiated actions that apply only their own change without affecting the pending update queue.

#### 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.