Esper Agent update via pipeline succeeds but Blueprint converge gets stuck "In Progress" on remaining devices in group

Android

After deploying an Esper Agent update to a device group, Blueprint converge requests may get stuck in In Progress or Queued state on some or all devices. This article explains how to resolve the issue and ensure your Blueprint settings are applied correctly.

Before you begin

Make sure your Esper Agent update pipeline has fully completed with a Completed status. Do not trigger Blueprint converge while the Agent update is still running—this can cause a race condition that leaves converge requests stuck.

Step 1: Wait for the Agent update pipeline to complete

1. Go to Esper Console → Software Updates.
2. Select the Esper Agent version you deployed.
3. Wait until the pipeline status shows Completed before proceeding to the next step.

Step 2: Cancel pending converge requests

1. Navigate to Devices & Groups → [Your Group Name].
2. Check if any Blueprint converge requests are still showing as Queued or In Progress.
3. If you find stuck requests, cancel them before triggering a new converge.

Step 3: Trigger a fresh Blueprint converge

1. After cancelling any pending requests, initiate a new Blueprint converge on your device group or on individual devices.
2. Wait for the converge to complete.
3. Verify that the converge status shows Success for all devices.

Step 4: Verify Blueprint settings are applied

1. Go to Devices & Groups → Device Details for each device.
2. Confirm that your Blueprint settings (wallpaper, configuration parameters, policies) are now visible and active on the device.

If converge requests continue to fail

Before contacting support, check the following:

• Device connectivity: Verify that the device is online and responsive. An offline or intermittently connected device will queue commands without executing them.
• Device status: Use Devices & Groups → [Device Name] → Actions → Collect Logs to gather Esper Agent logs. You can also use ADB to pull logs: adb shell logcat -d -s EsperDevicePolicy > dpc_logs.txt
• Drift state: If devices were in Drift state before the Agent update, they remain in Drift after the update. Trigger a converge to resolve the drift.

If a device shows Success in converge status but does not reflect the Blueprint settings visually or functionally, this indicates a state synchronization issue that requires investigation.

Still need help?

If the issue persists after following these steps, contact Esper Support and include the following information:

• Device serial numbers and model names
• Blueprint ID
• Esper Agent logs collected from affected devices
• The exact time the Agent update pipeline completed
• Whether the issue occurs consistently after Agent updates