Schedule your first maintenance

Maintenance windows differ from incidents in two ways: they are planned in advance, and Observer auto-transitions them through their lifecycle on a cron tick (so you do not have to remember to mark "started" / "completed" manually).

Steps

1. •

   Open the new-maintenance form

   In the console, navigate to Updates > Post update. Pick Maintenance as the type. The form replaces the severity field with a Scheduled start + Scheduled end pair.

2. •

   Set the window

   Pick the start and end times in your local timezone. The cron auto-transitions the maintenance through:

   • scheduled → in_progress when now() >= scheduled_start_at.
   • in_progress → completed when now() >= scheduled_end_at.

   A maintenance.starting_soon webhook fires one hour before scheduled_start_at (idempotent; once per maintenance row).

3. •

   Pick affected services

   The public page renders a banner for the maintenance starting within 24 hours and a sticky banner while in progress. The banner lists affected services so customers know which surfaces are impacted.

4. •

   Publish

   Maintenances always publish on save (drafts are an incident-only flow). The page banner appears within 24 hours of the scheduled start; subscribers receive maintenance.scheduled immediately and maintenance.starting_soon one hour out.

Cancel a scheduled maintenance

Open the maintenance row from Updates. The right-side rail has a Cancel action. canceled_at is set, the banner is removed, and the maintenance.canceled webhook fires.