Blueprint convergence fails with "Disable Updates" policy on non-Samsung/Lenovo devices

Android

When a Blueprint containing the "Disable Updates" System Update Policy is applied to non-Samsung, non-Lenovo Android devices (such as Redmi, OnePlus, or certain Lenovo models not in the supported set), those devices enter Drift mode and display the error: Blueprint application failed. Error(s) – [System update policy "Disable Updates" is not compatible on this device.]

Why this happens

The "Disable Updates" System Update Policy relies on OEM-specific Android management APIs that only Samsung and supported Lenovo devices expose. When the Esper Agent attempts to apply this policy on any other OEM device, the API call fails and Blueprint convergence stops entirely — even if every other setting in the Blueprint is compatible. Because the failure is device-specific rather than group-wide, mixed-OEM fleets often surface this problem only on a subset of devices.

Steps to resolve

Identify all affected devices. In the Esper Console, go to Devices & Groups and filter by Status: Drift. Open the Activity Feed for each drifted device and confirm the error reads System update policy "Disable Updates" is not compatible on this device. Note which Blueprint is applied to the affected group.
Open the Blueprint applied to the affected group. Go to Blueprints, locate the blueprint by name, and click Edit.
Change the System Update Policy to a cross-OEM compatible option. Under System Update Policy, replace Disable Updates with one of the following — all three are supported across all Esper-managed OEM devices:
- Automatic — updates install as soon as they are available
- Windowed — updates install only during a defined maintenance window you configure
- Postpone — defers updates for up to 30 days
Save and publish the updated blueprint. Click Publish to make the change active. Publishing is required before the update can be pushed to any device.
Trigger convergence on the affected devices. Go to Devices & Groups, select the affected group or individual devices, and select Converge. This forces the Esper Agent to re-apply the Blueprint immediately rather than waiting for the next scheduled sync.

Verify: In the Activity Feed for each previously drifted device, confirm a new Blueprint application event appears with no errors. All affected devices should exit Drift mode and show a status of In Sync within 5 minutes of triggering convergence.

Preventing this in mixed-OEM fleets

If your fleet spans multiple OEM brands, split devices into separate groups and assign OEM-specific Blueprints that only contain policies supported by that hardware. Use a base blueprint for settings common to all devices, and create separate blueprints per OEM that override only the policies — such as System Update Policy — that differ by device brand. This prevents a single incompatible setting from blocking convergence across an entire mixed group.

If this doesn't resolve it

If devices remain in Drift mode after convergence, or the Activity Feed shows a different error code, collect the following before contacting Esper Support:

The exact error message from the Activity Feed for at least one affected device
The device make, model, and Android version (visible under Devices & Groups → [Device Name] → Device Info)
The name and version of the Blueprint applied to the group
A screenshot of the System Update Policy section of the Blueprint

Contact Esper Support at support.esper.io with this information.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.