<< Click to Display Table of Contents >> Raynet One > 2026.4 > User Guide > Workspaces in the sidebar menu > Endpoint Management > Deployments  Rollout Waves

Rollout waves allow you to deploy packages to managed devices in a controlled, staged manner. Instead of targeting all devices simultaneously, the deployment is split into sequential waves, each covering a defined subset of devices. A subsequent wave starts only after the preceding wave meets the configured success criteria. This approach reduces the risk of widespread failures during a rollout and allows you to assess results before proceeding.

 

Wave configuration is available as an optional step in the deployment wizard when scheduling a package deployment job. You can configure waves manually or apply a Wave Template to reuse a predefined configuration.

 

Enabling Wave Configuration

In the deployment wizard, the Wave Configuration step is hidden by default. To enable it, turn on the Enable rollout waves toggle. Once enabled, the wave configuration grid becomes available and must be completed before the deployment can be started.

 

Wave Names

The first wave in a configuration is automatically named Pilot. Subsequent waves are named Wave 2, Wave 3, and so on. The final wave, which receives all remaining unassigned devices, is named Remainder.

 

Wave Configuration Grid

The wave configuration grid defines the individual waves that make up the rollout. Each wave card contains the following settings:

 

Sizing mode

Determines how the devices are assigned to this wave. The following sizing modes are available:

 

•By count: Assigns a fixed number of devices to this wave. Enter the number of devices in the Device count field.

•By percentage: Assigns a specified proportion of the total deployment target to this wave. Enter the percentage in the Percentage field.

•By explicit selection: Assigns specific devices that you select manually. Select the Select... button to open the device picker and choose the devices to include in this wave. Devices assigned to a wave with explicit selection are excluded from all subsequent waves.

•By explicit resource group: Assigns all devices that belong to one or more selected resource groups to this wave. Select the Browse resource groups... button to choose the resource groups. All devices that are members of the selected groups at deployment time are included in this wave.

•Remainder (automatic): The final wave automatically receives all devices that were not assigned to any earlier wave. A configuration always ends with a Remainder wave; you cannot manually configure the size of this wave.

 

The pool summary above the wave grid shows the estimated pool size (the total number of devices targeted by the deployment) and how many devices are assigned so far across all waves. If the total assigned count exceeds the pool size, an error is shown and the wizard cannot proceed.

 

Advanced Settings

Each wave has an Advanced settings section (expand it by selecting the chevron) that controls when the wave advances and when it halts:

 

•Advance threshold: The minimum percentage of successful installations required for the platform to advance to the next wave.

•Advance quorum: The minimum percentage of devices in the wave that must complete (successfully or not) before the advance threshold is evaluated. This prevents early advancement based on insufficient data.

•Halt threshold: The failure rate at which the wave is automatically stopped. Required to be greater than zero for the Pilot wave.

•Halt quorum: The minimum percentage of devices that must complete before the halt threshold is evaluated.

•Max duration: The maximum time allowed for the wave to complete. Enter the duration in ISO 8601 duration format (for example, PT1H for one hour, P1D for one day). The minimum value is one hour.

•Timeout policy: The action to take when the wave exceeds the configured max duration. Options are Continue (advance to the next wave regardless of results) or Halt (stop the entire deployment).

 

You can add multiple waves using the + Add wave button. The Remainder wave is always appended automatically and cannot be removed. The Pilot wave (the first wave) cannot be removed either.

 

Reactive Wave Throttle Settings

In addition to the per-wave settings, the reactive wave throttle controls the overall execution rate within an active wave. These settings apply globally to the wave execution and provide guardrails for high-volume deployments:

 

•Max concurrent runs: The maximum number of installations that may run simultaneously within a wave.

•Max total runs: The maximum total number of installation attempts within a wave, including retries.

•Halt threshold: The failure rate at which the wave is automatically halted. Defined as a percentage of total runs.

•Quorum: The minimum number of completed runs required before the halt threshold is evaluated. This prevents early termination based on insufficient data during the initial phase of a wave.

•Max duration: The maximum time allowed for the reactive throttle to operate within a wave.

•Timeout policy: The action to take when the reactive throttle max duration is exceeded — either Continue or Halt.

 

Wave Halt

A wave is halted automatically when its failure rate reaches or exceeds the configured Halt threshold while the number of completed devices meets or exceeds the configured Halt quorum. When a wave is halted, the entire deployment stops and does not advance to the next wave. The deployment status changes to Halted and the wave that triggered the halt is shown with a Halted status badge in the deployment details view.

 

A wave can also be halted if its Max duration expires and the configured Timeout policy is set to Halt. In this case the halt reason is a timeout rather than a threshold violation.

 

The progress of a wave-based deployment can be monitored from the Deployments section of the Endpoint Management workspace.