Blueprint 'Enforce Apps and Versions' not applying: devices stuck on outdated blueprint version

Android

If you've enabled Enforce Apps and Versions on a Blueprint but devices aren't updating to the enforced app version, the issue is likely that your devices are running an older Blueprint version. Blueprint changes don't automatically apply to enrolled devices — you need to manually trigger a Converge operation to push the updated Blueprint to your devices.

Understanding Blueprint versioning

Every time you save changes to a Blueprint, a new version is created in the Esper Console. However, devices that were already enrolled retain their last-applied Blueprint version. These changes — including new Enforce Apps and Versions settings — won't reach your devices until you explicitly run a Converge operation.

For example, if your Blueprint is now at version 38.0 but your devices are still on version 30.0, any configuration changes made between those versions (including app enforcement rules) have never been pushed to those devices.

How to apply Blueprint changes to your devices

1. In the Esper Console, go to Devices & Groups.
2. Click Filter, select Blueprint, choose the Blueprint name, and click Apply.
3. Review the filtered device list. Check the Blueprint version column and compare it against the latest published version in your Blueprint settings.
4. Select all filtered devices by clicking Select All.
5. Click Actions → Converge.
6. Confirm the Converge operation. This pushes the latest Blueprint version (including your Enforce Apps and Versions configuration) to all selected devices.
7. After Converge completes, return to the filtered device view and verify that all devices now show the latest Blueprint version number.
8. Spot-check a few devices by going to Devices & Groups → [Device Name] → Apps to confirm the enforced app version is now installed and active.

What if devices are offline?

If devices are offline when you run Converge, the Blueprint update will be queued and applied automatically when the device reconnects to the Esper platform. Monitor your device status and check again after connectivity is restored.

Devices show the new Blueprint version but apps still aren't updating

If Converge succeeded and devices now have the latest Blueprint version, but the app version still hasn't changed, check the following:

• Verify the correct app version is specified in Enforce Apps and Versions and that the APK or Play Store version is available in your enterprise app catalog.
• Confirm the app is marked as Required — optional apps are not actively enforced.
• Check that your devices have stable connectivity to the Esper platform. Apps will update once the device is online and connected.

Best practices for Blueprint changes at scale

If you manage thousands of devices, consider converging in batches using Groups rather than all at once. This prevents simultaneous load on your devices and the Esper platform.

Additionally, make it a habit to run Converge immediately after publishing Blueprint changes. This prevents Blueprint version drift, where devices gradually fall further behind the latest configuration.

Still need help?

If your devices still aren't updating after following these steps, or if Converge operations complete without errors but your device Blueprint version doesn't update, contact Esper Support. Include the Blueprint name, the number of affected devices, and the version gap you're seeing (e.g., devices on v30.0 but latest is v38.0).