Devices stuck in Blueprint Drift with Converge IN_PROGRESS after Group migration

Android

Title: Devices stuck in Blueprint drift showing IN_PROGRESS after group migration

After migrating devices to v3 Groups and assigning a Blueprint with a large number of new apps or policy changes, affected devices show a persistent Blueprint drift status of IN_PROGRESS and associated commands appear as Command Queued in the Esper Console without executing.

Why this happens

When a device moves to a new group, the Esper Agent must process the full delta between the device's current state and the assigned Blueprint. If that delta includes 15 or more new apps or significant policy changes, the command processing pipeline needs extra time to stabilize after the group reassignment. Until the pipeline is ready, commands queue but do not execute, which makes the device appear stuck.

Steps to resolve

1. Confirm the device is online. Navigate to Devices & Groups → [Device Name] → Overview and verify the device shows an active connection. A device that is offline cannot process queued commands regardless of Blueprint status.
2. Wait for processing to complete. Allow up to 2 hours after the group migration before treating the IN_PROGRESS status as a true failure. Large Blueprint payloads routinely take this long to fully converge, and intervening too early can interrupt the process.
3. Check convergence status after the waiting period. Go to Devices & Groups → [Device Name] → Blueprint and confirm whether the drift indicator has cleared and all Blueprint apps are installed. If the device has converged, no further action is needed.
4. Re-apply the Blueprint manually if the device is still stuck after 2 hours. On the same Devices & Groups → [Device Name] → Blueprint screen, select Apply Blueprint. This forces a fresh convergence attempt and clears any stalled command queue entries. Monitor the device for 15–30 minutes afterward.
5. Check for offline devices if multiple devices in the same group are affected. Return to Devices & Groups → [Group Name] and review the online status of all group members. If several devices are offline, restore connectivity and allow 30 minutes for queued commands to begin processing once they reconnect.
6. Collect device logs if commands still do not execute. Connect to the device via ADB and run the following command to capture Esper Agent logs:

   adb shell logcat -d -v time > esper_agent_logs.txt

   Search the output for errors related to converge or command dispatch to identify where processing is failing.

Verify: The device's Blueprint screen under Devices & Groups → [Device Name] → Blueprint should show no drift indicator and a converged status within 2 hours of migration. All apps defined in the Blueprint should be visible and installed under Devices & Groups → [Device Name] → Apps.

If this doesn't resolve it

If the device remains in IN_PROGRESS after re-applying the Blueprint and confirming the device is online, contact Esper Support with the following information:

• Device name and serial number
• Blueprint name and Blueprint ID
• Converge IDs shown on the Blueprint screen
• The ADB log file captured in Step 6
• Approximate time of the group migration

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.