Skip to main content
Enterprise customers often request the ability to control when updates can occur in their environments. Maintenance windows satisfy this requirement by letting them define specific time periods when automated updates are allowed, helping them feel more comfortable with continuous deployment practices.

​
Understanding Maintenance Windows

Maintenance windows address common enterprise customer concerns about continuous deployment:
  • Control over when changes can occur in their environment
  • Predictability around update schedules
  • Protection of peak business hours
  • Alignment with their existing change management processes

​
Configuring Maintenance Windows

To configure maintenance windows for your environment:
1

Navigate to Environments

Go to the Environments tab in the Ryvn Dashboard
2

Select Environment

Choose the environment you want to configure
3

Access Maintenance Windows

Click on the Maintenance Windows section
4

Add New Window

Click Add Maintenance Window
5

Configure Window

  1. Set the start time (e.g., 22:00)
  2. Set the end time (e.g., 04:00)
  3. Select the timezone from the dropdown menu
  4. Select the checkboxes for each day you want the maintenance window to be active
6

Save

Click Save to apply your configuration
All times are specified in 24-hour format and must include a timezone. Updates will only start during these windows.

​
How Maintenance Windows Work

When a maintenance window is configured:
1

Schedule Definition

Your customer specifies their preferred update times based on their operational requirements.
2

Update Queueing

Updates that arrive outside the maintenance window are queued until the next available window.
3

Execution

When a maintenance window begins, any queued updates are automatically applied.
Automated rollbacks with health check monitoring are available as an enterprise feature. Contact us to learn more.

​
Types of Updates

The following updates respect maintenance windows:
Update TypeDescription
Platform UpdatesOperating system and runtime updates
Security PatchesCritical security fixes
Infrastructure ChangesUnderlying infrastructure modifications
Automated DeploymentsIf configured, automated deployments from your repository
Critical security updates may be applied outside maintenance windows if necessary to protect your environments. Customers are always notified when this occurs.

​
Best Practices

Many enterprise customers have existing change management processes. Work with them to understand these processes and configure windows accordingly.
Create windows of at least 4 hours to ensure updates can complete without rushing.
Global enterprises may need different windows for their various regions and time zones.
Keep customers informed about planned updates. Clear communication helps them trust the continuous deployment process.

​
Monitoring Updates

Customers can track update activities in the Activity tab of their environment:
  • Scheduled updates waiting for the next window
  • Updates in progress during active windows
  • Completed update history
Updates that start during a maintenance window will complete even if they extend beyond the window’s end time.