> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/details/details-page-options/maintenance-indicators.md).

# Maintenance indicators

### Overview

This page shows the indicators in place for current and past maintenance periods.  [Putting watches into maintenance windows is an admin task.](https://support.highlight.net/help/admin/create_container#maintenance_tab) &#x20;

{% hint style="info" %}

#### In maintenance  <picture><source srcset="/files/DCPpkgHz04jexgzIfnFF" media="(prefers-color-scheme: dark)"><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2FCViS6LWYg2N9DvcFvfdE%2FMaintenaceIndicator-Light.png?alt=media&amp;token=5431162d-fd2c-4785-a629-96d7b3f26749" alt="Maintenance indicator"></picture>

Watches in maintenance do not send alerts, change the colour of heat tiles nor decrement availability figures
{% endhint %}

### Details page - Header

When a watch is in maintenance, the maintenance icon shows in the header

<figure><picture><source srcset="/files/Om4iMKsPJ82LfhmWIxS4" media="(prefers-color-scheme: dark)"><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2F6bqIlN71yZBFl03riR8s%2FDetailsHeaderMaintenance-light.png?alt=media&amp;token=3c8364b0-f1a7-4c81-9265-dd13bbf4a84c" alt="Details page Maintenance indicator"></picture><figcaption></figcaption></figure>

Hover on the maintenance icon to see:

* the name of the container/maintenance window ("Maintenance ON 24x7 Container" in the image)
* the time remaining in the maintenance window ("9h 14m" in the image); less than one minute remaining will show as "<1m"
* if you see a number in brackets (2), this means there's more than one maintenance window in effect for this watch. The time remaining is when the first maintenance window is due to end. This time will then adjust to show how long until the next maintenance window is due to end.

### Details page - Background colours

Find out more about [Details page background colours](/details/details-page-options/background-colours.md#maintenance-periods-purple-backgrounds).&#x20;

### Details page - Performance test

<figure><picture><source srcset="/files/zT1kxaeX8p63JGXB4Lov" media="(prefers-color-scheme: dark)"><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2F1kAVpDnXXvPBSXOyTEiW%2FPerfChartMaintenance-light.png?alt=media&amp;token=692d79d3-c8ce-41f4-bf16-03c5874054e5" alt="Details page performance chart in maintenance"></picture><figcaption></figcaption></figure>

When a performance test is in maintenance, you will see a purple background area on the chart and a marker showing:

* the maintenance icon&#x20;
* the name of the maintenance window ("Maintenance ON 24x7 Container" in the image above)
* the time remaining in the maintenance window (8h 29m in the image above). If it's less than one minute remaining, "<1m" shows.
* if you see a number in brackets (2), this means there's more than one maintenance window in effect for this test. The time remaining is when the first maintenance window is due to end. This time will then adjust to show the next maintenance window in effect.


---

# 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://help.highlight.net/details/details-page-options/maintenance-indicators.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.
