Skip to main content
Learn more about Maintenance Windows in the Maintenance Windows documentation.
Use Maintenance Windows to schedule planned maintenance periods that prevent your checks from running and triggering alerts during expected downtime.

Configuration

MaintenanceWindow Options

string
required
A name for the maintenance window that will be displayed in the Checkly dashboard and used for identification.Usage:
Use cases: Window identification, dashboard display, maintenance tracking.
string[]
Tags that filter which checks are affected by this maintenance window. Checks with ANY of these tags will be paused during the maintenance period to avoid unnecessary alerts. Not needed when pauseAllChecks is true.Usage:
Maintenance windows affect ALL checks that have ANY of the specified tags. Be specific with your tags to avoid affecting unintended checks.
Use cases: Service targeting, environment isolation, maintenance scope control.
Date
required
Start date and time for the maintenance window in UTC (ISO 8601 timestamp).Usage:
Use cases: Scheduled downtime, emergency maintenance, recurring maintenance timing.
Date
required
End date and time for the maintenance window in UTC (ISO 8601 timestamp).Usage:
Use cases: Maintenance duration control, downtime limitation, schedule coordination.
number
Repeat interval from the first occurrence. Used with repeatUnit to create recurring maintenance windows.Usage:
Use cases: Regular maintenance scheduling, automated recurring downtime, consistent maintenance intervals.
string
Repeat strategy that defines the time unit for recurring maintenance windows (DAY | WEEK | MONTH).Usage:
Examples:
Use cases: Time-based recurrence patterns, maintenance scheduling consistency, automated repetition.
Date
When to stop repeating the maintenance window (ISO 8601 timestamp in UTC). If not specified, the maintenance window will repeat indefinitely.Usage:
Use cases: Limited-time maintenance periods, project-based scheduling, planned end dates.
string
The named IANA time zone used to schedule recurring occurrences, for example "America/New_York". Occurrences keep the same local time across daylight-saving changes; see Timezones and daylight saving. Editors suggest known zone names as you type.startsAt and endsAt stay absolute instants: the time zone does not reinterpret them, it only decides how later occurrences follow local time. UTC offsets such as "+05:00" or "Etc/GMT+5" are not accepted. Defaults to UTC.Usage:
The CLI always sends the time zone on deploy. If you remove timezone from your code, or a time zone was set for the window in the Checkly UI, the next deploy resets the window to UTC. A time zone can’t be changed while a maintenance is active, so a deploy that changes it during an active maintenance fails until the maintenance ends.
Use cases: Maintenance tied to local business hours, recurring windows that must survive daylight-saving changes.
boolean
default:"false"
Pause every check in the account during the maintenance window, regardless of tags.Usage:
Use cases: Account-wide migrations, full platform downtime.
string[]
Tags that filter which checks have their alerts silenced during the maintenance window. Silenced checks keep running and collecting data, but alert channels aren’t notified. Ignored when silenceAllAlerts is true.Usage:
Use cases: Keep monitoring during expected degradation without noisy alerts.
boolean
default:"false"
Silence alerts for every check in the account during the maintenance window, regardless of silenceAlertsTags. Checks keep running.Usage:
Use cases: Account-wide alert silencing while monitoring continues.

Examples

Best Practices

Tag Matching: Maintenance windows affect ALL checks that have ANY of the specified tags. Be specific with your tags to avoid affecting unintended checks.
Time Zones: Always use UTC timestamps for consistency across different time zones. Convert your local maintenance times to UTC.