> 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/iz-pulse/maintenance-window.md).

# Maintenance Window

A maintenance window refers to a designated period of time during which planned maintenance activities or system updates are performed. Maintenance windows can be performed on a **`Status Page`**, **`Category`** or **`Endpopint`**. Maintenance windows are commonly scheduled during periods of low user activity to minimize the impact on users and business operations.

Communication with stakeholders is crucial during the planning and execution of maintenance windows to inform users about potential downtime or disruptions. All users subscribed to the **`Status Pages`** will receive the maintenance window updates.

### Maintenance Windows

1. Navigate to **`IZ Pulse`** -> **`Maintenance Window`** <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FrhED7eeZPzhznZT9LKuH%2Fmaintenance_windows.png?alt=media&amp;token=59ddc1c4-42f4-4913-b4ce-394edfa78961" alt=""><figcaption></figcaption></figure>
2. Each maintenance window is associated with -
   1. Start time - Start date and time of the maintenance window
   2. End time - End date and time of the maintenance window
   3. Name - Name of the maintenance window
   4. Description - Description of the maintenance window
   5. Notify Before - Duration in minutes before which the notification should be sent to subscribed users
   6. Status Pages - Endpoints in the status page which will be under maintenance
   7. Categories - Endpoints in the categories which will be under maintenance
   8. Endpoints - Endpoints which will be under maintenance
3. Click on the **`Configure Window`** action to create a new maintenance window. Refer to [Configure Maintenance Window](/product-guides/integral-zone/iz-suite/iz-pulse/maintenance-window/configure-maintenance-window.md).

### See Also

* [Configure Schedule](/product-guides/integral-zone/iz-suite/iz-pulse/configure-schedule.md)
* [Categories](/product-guides/integral-zone/iz-suite/iz-pulse/categories.md)
* [Status Pages](/product-guides/integral-zone/iz-suite/iz-pulse/status-pages.md)


---

# 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/iz-pulse/maintenance-window.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.