Scheduled app swap across all devices using Blueprint update + timed convergence

Android

Learn how to schedule an app replacement across your entire device fleet at a specific date and time using Blueprint updates and scheduled convergence. This approach ensures all devices update simultaneously without requiring manual intervention at cutover.

Before you begin

Confirm that:

• You have access to Blueprints in the Esper Console.
• You know which Blueprints include the app you want to replace.
• You have the app ID or URL for the replacement app.
• Your cutover date and time are confirmed, and you know your timezone.

Step 1: Update your Blueprint with the new app

1. In the Esper Console, go to Blueprints.
2. Open each Blueprint that currently includes the app you want to replace. If all your devices use a single Blueprint, you only need to update that one.
3. In the Apps section, locate and remove the existing app entry.
4. Add the replacement app, making sure the app ID or URL is correct.
5. Save the updated Blueprint.

Note: If your devices are distributed across multiple Blueprints, you must update each Blueprint individually. There is no single action to replace an app across all Blueprints at once.

Step 2: Schedule Blueprint convergence

1. From the Blueprint you just updated, locate the Converge option.
2. Select Schedule Convergence.
3. Set the target date and time to match your cutover window (for example, July 14th at 2:00 PM).
4. Verify that all device groups you intend to update are associated with this Blueprint.
5. Save and confirm the scheduled convergence.

Important: Double-check your timezone to ensure the convergence fires at the correct time relative to your backend migration.

Step 3: Verify the schedule

1. Review the convergence schedule summary to confirm the date, time, and device scope.
2. Verify that no devices are pinned to an older Blueprint version, which would prevent the update.

Step 4: Verify the app swap after cutover

After the scheduled convergence runs:

1. Go to Devices & Groups in the Esper Console.
2. Select a device from your target fleet.
3. Confirm that the device reflects the updated Blueprint version.
4. Verify that the new app is installed and active, and the old app is no longer present.

Troubleshooting

Convergence did not fire at the scheduled time:

• Check whether your devices were online during the convergence window. Devices that are offline will receive the update when they reconnect.
• Verify the timezone setting in your console is correct.

Only some devices updated:

• Confirm all targeted devices are associated with the correct Blueprint version. Devices on different Blueprints or older pinned versions will not be affected.

The new app did not appear on devices after convergence:

• Verify the new app was added with the correct app ID or URL.
• Confirm the Blueprint was saved before the convergence was scheduled.
• Ensure the devices came online after convergence ran.

Important considerations

• Devices must be online during the convergence window (or come online shortly after) to receive the update. Devices that remain offline indefinitely will update only when they reconnect.
• Blueprint convergence applies your entire Blueprint desired state. Review all Blueprint settings—policy configurations, kiosk settings, and other options—to ensure no unintended changes are deployed when convergence runs.
• This workflow works with any Android device managed through Esper Blueprints, regardless of device model or OEM.

Still need help?

If the scheduled convergence triggers but devices do not reflect the updated app state after coming back online, or if you encounter other issues, contact Esper Support.