# Recurring maintenance

Organizations sometimes have maintenance windows that occur repeatedly—for example, the first Monday or the 1st of every month.

Recurring maintenance tasks allow you to automate such cases and save time reporting the same maintenance window multiple times.

### Setup

In order to configure a recurring task, you'll first need to have what we call a "maintenance base," meaning maintenance that you have reported before with the details you'd like to see in the automatically reoccurred maintenance.

Create a maintenance by clicking on the <mark style="background-color:green;">command bar button</mark> (or simply typing `CMD`/`CTRL`+`K`) and selecting `Create new maintenance`.

{% hint style="info" %}
Read more about reporting a maintenance under [Step 5 - Report an incident](/get-started/step-5-report-an-incident.md)
{% endhint %}

Once you have your maintenance base created, head over to the "Recurring tasks" page (by clicking on <mark style="background-color:green;">Incidents > Recurring tasks</mark>) and click on `New recurring task`.

<figure><img src="/files/Yvsr1LLXZhnWEUbAWM8A" alt="status page new recurring maintenance task"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.statuspal.io/monitoring-and-automation/recurring-maintenance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.