Skip to main content

Automated Rollouts

info

💡 Learn more about this strategy in our Automated Rollouts announcement blog post!

This feature automates the mobile app (Android and iOS) release rollout process.

Instead of manually releasing, rolling out, and monitoring crash rates you can rely on Automated Rollouts to:

  1. Start the rollout process by releasing the app to a subset of users.
  2. Detect potential issues (crash rate greater than 1%) during the rollout.
  3. Automatically halt/pause the rollout when predefined thresholds have been exceeded.
  4. Notify your team of any problems, so you can quickly address them.

Prerequisites

For this feature to be enabled, there are two prerequisites

With these in place, you can now enable Automated Rollouts for the desired app!

Setup

Enable Automated Rollouts for Android

In Wolfia, navigate to the Android app settings by clicking the gear icon next to the selected app.

Android app settings

In the Android app settings, under Sentry Project Connection, select Automatically halt staged rollout if crash rate exceeds threshold.

iOS app settings - Automated Rollouts

Click Update to save the changes.

The next time your release your app to the production track, the rollout will be monitored and automatically halted if needed.

Enable Automated Rollouts for iOS

In Wolfia, navigate to the iOS app settings by clicking the gear icon next to the selected app.

iOS app settings

In the iOS app settings, under Sentry Project Connection, select Automatically pause phased releases if crash rate exceeds threshold.

iOS app settings - Automated Rollouts

Click Update to save the changes.

The next time your release your app to the production track, the rollout will be monitored and automatically paused if needed.

How it works

How is the crash rate determined?

The crash rate is calculated by comparing the number of session with crashes to the number of total sessions for the given release for the trailing 24 hours based on Sentry health data.

  • Healthy: the session crash rate is below 1%. The release is considered healthy and the rollout will continue.
  • Insufficient data: less than 5 sessions (or none) for the release in the last 24 hours. The release health is unknown and the rollout will continue to collect more data for the next health check.
  • Unhealthy: the session crash rate exceeds 1%. The release is considered unhealthy and rollout will be halted/paused.

For example, if a release is currently being rolled out and in the last 24 hours it's had 400 total sessions, where 3 of those sessions had crashes, the crash rate is 0.75% and the release is considered healthy.

If there were 5 sessions with crashes, the crash rate would be 1.25% and the release would be considered unhealthy and the rollout would be halted/paused.

How often is the crash rate checked?

  • For iOS phased releases, this is checked for active rollouts every 15 minutes.
  • For Android staged rollouts, this is checked for active rollouts every 24 hours before incrementing the rollout percent to the next in the schedule.