Rollouts, pause and rollback

Start at 1–10%. Each device gets a stable bucket from its installation ID, so raising the percentage only adds devices — no device flips back and forth.

Stops offering the release to devices that do not have it yet. Devices that installed it keep it.

Requires a reason. The channel returns to the previous release (or one you choose with the same runtime) and devices move to it on their next check. Release files are never deleted by a rollback.

Once at least 25 devices have reported an install outcome and the failure rate passes the rollout's threshold (2% by default), the release pauses itself and your team is notified.