Management of maintenance blackouts

You can manage important updates to ensure that tasks run smoothly without interfering with ongoing deployments by using maintenance blackouts. You can manage maintenance blackouts by creating a recurrence blackout, rescheduling an existing blackout, creating a specific environment blackout, and canceling an existing blackout.

You can schedule a maintenance blackout in the daily, weekly, or monthly recurrence pattern. When a recurring scheduled deployment is created, its events are now linked together into a series.

You can update a maintenance blackout by modifying the name and description and rescheduling an upcoming maintenance blackout of a recurrent deployment series.

Rescheduling an upcoming recurring maintenance blackout changes the timing of subsequent events in the same series. For example, if the daily blackout series is moved from 7 pm to 8 pm, all future blackouts are also moved to 8 pm. Similarly, if the blackout is extended from 1 hour to 2 hours, the duration of all subsequent blackouts is extended to 2 hours.

Note: Suppose a maintenance blackout is rescheduled to a later date, any events that were scheduled before that date are removed. Recurrences that were canceled on a specific date remain canceled. For example, if the blackout event for next Monday is canceled due to a holiday, and later the Tuesday blackout is rescheduled to Wednesday, then the blackout on Monday remains canceled.

If a recurring deployment is rescheduled, the dates and cancellations of future deployments are adjusted in the same way as recurring maintenance blackouts. However, if the recurrence pattern is changed, then the cancellations are reset.

Entire recurrence series or individual events can be canceled without affecting the rest of the events in the series.