Blueprint converge failure reason not visible in console UI: engineering fix deployed (Chrome 148 affected)

Android

If you can't see the failure reason when a Blueprint converge operation fails in the Esper Console, or if your Blueprint is failing to converge due to System Update Policy settings, this article will help you resolve both issues.

Before you begin

This article covers two separate problems that can occur together:

• The Esper Console doesn't display failure details when you click the converge status link (a console rendering issue)
• Your Blueprint converge is failing with a System Update Policy error

You may experience one or both of these issues. Follow the relevant sections below.

How to view Blueprint converge failure details

If you see a converge failure status but the failure detail panel appears blank when you click it, follow these steps:

1. Hard-refresh your browser cache. In Chrome, press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac).
2. Navigate to Blueprints → [Blueprint Name] → Converge History.
3. Click the status link in the converge result column (for example, 1/1).
4. Verify that the failure reason panel now displays the affected device and the specific error message.

If the panel is still blank after refreshing, try clearing your browser cache entirely and repeat these steps.

How to fix converge failures related to System Update Policy

If your converge is failing with an error like Blueprint application failed due to - [System update policy Disable Updates is not compatible on this device.], your Blueprint's System Update Policy setting is not compatible with the target device. Follow these steps:

1. Navigate to Blueprints → [Blueprint Name] → Edit Blueprint.
2. Locate the System Update Policy setting.
3. Change the value from Disable Updates to either Automatic Updates or Scheduled Updates.
4. Save the Blueprint.
5. Trigger a reconverge on the affected device(s) by navigating to Devices & Groups → [Device Name] → Blueprint → Apply / Reconverge.
6. Wait for the reconverge to complete and verify the status shows success.

Not all Android device models support the Disable Updates policy. Device manufacturer (OEM) implementation of Android Device Policy Manager APIs varies, which may prevent this policy from being applied to certain devices.

If the converge still fails after changing the System Update Policy

If switching to Automatic Updates or Scheduled Updates doesn't resolve the issue:

• Review all other Blueprint settings for additional configurations that may be incompatible with the specific device model.
• Request a bug report from the device by navigating to Devices & Groups → [Device Name] → Bug Report to gather diagnostic information.
• Note your device model, Android version, and Esper Agent version for your support ticket.

Still need help?

If the failure details remain blank after refreshing your browser, or if your converge continues to fail after updating the System Update Policy, contact Esper Support. Include the following information:

• Your Chrome version (or browser and version if you're using a different browser)
• The device model, Android version, and Esper Agent version
• A screenshot of the blank failure panel (if applicable)
• The exact error message from the Blueprint converge failure