Converge takes 45+ minutes to complete / How to cancel queued or initiated commands on a device
Android
Title: Blueprint convergence stalled — clear queued commands to speed it upWhen a Blueprint is applied to a device, convergence can take 45 minutes or longer if a backlog of commands has built up in the device's queue.
Why this happens
Every change a Blueprint applies — app installs, policy updates, configuration changes — is sent to the device as an individual command. Commands are processed one at a time in sequence, so if a device has been offline, reconnected after a long gap, or received frequent Blueprint updates, hundreds of commands can accumulate. The device must work through each one before Esper marks it as Converged.
Check the current command queue
- Open the Esper Console and go to Devices & Groups.
- Click the device name to open its detail view.
- Select the Activity Feed tab.
- Review the listed commands and note the state of each one. Commands move through three states: Queued → Initiated → Succeeded / Failed. Only commands in Queued state can be cancelled from the Console; commands in Initiated state cannot.
Cancel queued commands
- In the Activity Feed tab, locate every command showing a status of Queued.
- Select a queued command and choose the cancel action. Cancelling queued commands removes them from the processing backlog immediately, allowing the remaining commands to execute faster.
- Repeat for each remaining Queued command until the queue is clear.
- Monitor the Activity Feed to confirm each cancellation registers before moving to the next.
What to do when commands are stuck in Initiated state
Commands in Initiated state cannot be cancelled from the Esper Console. If one or more Initiated commands are blocking convergence, collect the following information before contacting support:
- Device ID or serial number (visible under Devices & Groups → [Device Name] → Device Information)
- The command IDs of all stuck commands (visible in the Activity Feed tab)
- The date and time convergence started
If this doesn't resolve it
If convergence remains stalled after the queue is cleared, or if commands are stuck in Initiated state, contact Esper Support with the following details:
- Device ID and serial number
- Command IDs of any stuck Initiated commands
- The date and approximate time convergence began
- Whether the issue affects a single device or multiple devices in your fleet
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.
Please sign in to leave a comment.
Comments
0 comments