> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/maintenance-windows.md).

# Maintenance Windows

A maintenance window marks a period of planned work on some services. While it runs, checks on the covered monitors still run but do not count as down, and the time is left out of service objective measurements. The window's name is shown on the public status pages that list a covered service, and subscribers are notified ahead of the start.

Open it from **Workspaces** → **Service Health** → **Maintenance windows** in the sidebar.

{% hint style="info" %}
Requires the **Service Health** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FXoIdoqLfzGMIT3F5aniu%2Fv2-sh-maint-list.png?alt=media&amp;token=82aaf4b4-9b53-46f5-90aa-614f9f0221b5" alt="Maintenance windows list"><figcaption><p>Maintenance windows</p></figcaption></figure>

## Maintenance Windows List

Use the **Status** filter to show **All**, **Scheduled**, **In progress** or **Completed** windows; **Save filters** keeps a combination to pick again from **Saved filters**. The list has a search box, **Refresh**, **Columns** and **Export**.

| Column                 | Description                                           |
| ---------------------- | ----------------------------------------------------- |
| **Maintenance window** | Window name. Click it to review the window.           |
| **Announcement state** | **Scheduled**, **In progress** or **Completed**.      |
| **Starts**             | Start time.                                           |
| **Ends**               | End time.                                             |
| **Actions**            | **Review window**, and delete for a scheduled window. |

## Plan a Maintenance Window

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1GAGpjs9XZpyp3lnZc2A%2Fv2-sh-maint-plan.png?alt=media&amp;token=ca654bcf-e2ef-45fc-80fd-ef3baee43f5a" alt="Plan a maintenance window drawer"><figcaption><p>Plan a maintenance window</p></figcaption></figure>

1. Click **Plan maintenance**.
2. Fill in **Purpose and impact** and **Timing and communication** (fields below). **Planned duration** and **Announcement due** update as you type.
3. Click **Save timing and select services**.
4. Under **Affected services**, choose a **Target type**: **Monitor version**, **Monitor category** or **Status page**.
5. Search in **Find a maintenance target** and click **Add selected service**. Repeat for each affected service. Each addition saves on its own.
6. Check the saved list, then click **Close**.

| Field                                | Description                                                                                                                                                   |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Window name**                      | **Required.** Up to 100 characters. Shown on public status pages that list a service this window covers.                                                      |
| **Purpose and expected impact**      | **Required.** What is changing, the expected disruption and recovery steps. Not shown on public status pages.                                                 |
| **Start time**                       | **Required.** Must be in the future. Times are entered in your browser's time zone, shown above the fields.                                                   |
| **End time**                         | **Required.** Must be after the start.                                                                                                                        |
| **Notification lead time (minutes)** | **Required.** How long before the start the window is announced, from 0 to 43,200 minutes. Default `30`. Subscriptions control who receives the announcement. |

To take a service out of a window, click **Remove service** on it. The monitor itself is unchanged.

## Review a Window

Click **Review window** on a row to see its purpose, timing and affected services. Click **Save timing changes** after changing the timing.

{% hint style="warning" %}
Only a **Scheduled** window can be changed or deleted. Once it is in progress or completed it is available for review only. You need a role that can create, edit or delete maintenance windows for those actions.
{% endhint %}

## Next Steps

* [Status Pages](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md): see how the window appears to your audience.
* [Service Objectives](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/service-objectives.md): maintenance time is left out of availability.
* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): check which monitors are in **Maintenance mode**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/maintenance-windows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
