Steps
- On Maintenance, choose what the window covers and give it a title. The title and the details are shown on the public status page while Show on the public status page is on; off keeps the window private.
- Under Repeats, choose Once and the start and the end, or Every week and the weekdays, the start time and the length. Times are in the time zone you pick, and a weekly window follows that zone’s clock changes.
- Press Schedule. A weekly window makes its next occurrences ahead of time. End now closes a running window early; Cancel removes the ones that have not started and ends a running one.
What it does and does not do
- Checks are not paused. Their results are stored, so you can still see what happened during the work.
- A window cannot start in the past, lasts from 5 minutes to 7 days, and an organisation keeps up to 100 schedules.
- A day that was only maintenance is shown in blue on the status page, never as green and never as downtime. The monthly report says how much time was left out and why.
- A failure that goes on after the window ends is judged normally from then on.
- The window does not send anything to your client by itself. Visitors see it on the status page; e-mail subscribers are mailed about incidents and about the updates you write (how).
Who can do it
Owners, admins and members schedule and change windows; viewers can read them. A script can open a window before a deploy through the API with a write key (API keys).