DeployPulse

Automatic Rollback

DeployPulse monitors error reports from devices and automatically rolls back a release if the error rate exceeds a configured threshold within a time window.

Auto rollback is available on paid plans. Upgrade your subscription on the DeployPulse billing page to enable this feature.

How it works

  • Error rate is calculated as DeploymentFailed / (DeploymentFailed + DeploymentSucceeded) events reported by the SDK
  • Checks run every 5 minutes across all enabled deployments
  • If the rate exceeds your threshold within the configured time window → the deployment rolls back to the previous release and an email notification is sent
  • A distributed lock prevents duplicate rollbacks across multiple server instances

Configuring auto rollback

Auto rollback is configured per deployment from the dashboard:

  1. Dashboard → select your app → select the deployment → Edit Deployment
  2. Scroll to the Auto-Rollback section (visible in edit mode only)
  3. Configure:
    • Enable/disable toggle
    • Error rate threshold - percentage of failed installs that triggers a rollback (e.g. 10%)
    • Time window - how far back to look when calculating the error rate (5 minutes – 24 hours)

The SDK must call codePush.notifyAppReady() after a successful update to report a success event. Low-traffic deployments may not accumulate enough data for accurate triggering - consider a longer time window or higher threshold for low-volume apps.

What happens on rollback

  • The previous release becomes the active release for that deployment
  • An email notification is sent to the account owner with the deployment name, the rolled-back label, and the new active label
  • The rollback appears in the release history for the deployment