> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Maintenance windows

> Schedule planned downtime so deploys and migrations don't open incidents or page your team.

A maintenance window is a time range where you expect a monitor to be down and don't want to hear about it. During the window, consensus suppresses incident creation, so a planned deploy or migration doesn't open an incident or fire an alert.

## Create one

In **Settings → Maintenance**, set:

* The **monitor** it applies to, or leave it unset to cover every monitor in the workspace.
* A **start** and **end** time. The end must be after the start.
* An optional **reason**, so the rest of the team knows what it was for.

Inside that range, the targeted monitors can fail freely and no incident opens. Outside it, monitoring is back to normal.

## What it does and doesn't do

A window suppresses incident creation. The checks keep running, so you can still watch the monitor's live state during the work; Tallwatch just won't turn failures into incidents or alerts.

<Warning>
  A maintenance window only suppresses incidents that would open during the window. An incident that's already open when the window starts is not auto-resolved. Resolve it from the incident page if you opened it before scheduling the work.
</Warning>

## No recurrence, by design

Windows are one-off records. There's no repeat or recurring schedule, and no edit: a window is a short-lived declaration of "ignore this monitor between these two times." If you got the time wrong, delete it and create a new one. For an open-ended silence rather than a bounded one, [pause the monitor](/monitors/creating-monitors#pausing) instead.