App stuck in "Failed to Download" loop due to multiple pending install commands: reboot device to clear command queue

Android

When multiple app install commands accumulate in a device's command queue, the Esper Agent repeatedly attempts the same installation and fails with the error The App - com.your.package Failed To Download. Network Issues Or An Expired Download URL Usually Cause This. Multiple Installations Are Ongoing. Attempt Again Shortly. — even after the device is rebooted or the app is removed.

Why this happens

Each time an install is triggered — whether manually, through a Blueprint, or by a retry — Esper queues a command on the device. If a previous install stalled (due to a brief network drop or a slow CDN response), new commands stack behind it. The device cannot process any of them, so every subsequent attempt fails with the same download error.

Steps to resolve

1. Confirm the command queue is the cause.
   In the Esper Console, navigate to Devices & Groups → [Device Name] → Activity Feed and look for repeated install events for the same app package within a short time window. Multiple entries confirm that duplicate commands are queued.
2. Verify the app version has a valid download URL.
   Go to Apps & Configuration → Apps → [App Name] → Versions and confirm the version you are deploying is listed without any upload errors. A corrupt or incomplete APK upload can trigger repeated retries. If the version appears invalid, delete it, re-upload the APK, and publish a new version before continuing.
3. Check network connectivity on the device.
   Confirm the device has stable access to the internet. If the device is behind a firewall or proxy, verify that Esper's CDN endpoints are not blocked and that DNS resolution is functioning correctly. A restricted network causes the initial download to stall, which is what seeds the command queue backlog in the first place.
4. Download the Esper Agent logs before rebooting.
   Go to Devices & Groups → [Device Name] → Actions → Esper Agent Logs and download the latest log bundle. Search the logs for entries containing Found pending install command or Multiple install commands detected to confirm the root cause and retain evidence before the queue is cleared.
5. Reboot the device to clear the command queue.
   Go to Devices & Groups → [Device Name] → Actions → Reboot and issue the reboot command. A reboot flushes the stalled command queue and allows the Esper Agent to re-register cleanly with the backend. Allow 3–5 minutes for the device to come back online and the Agent to stabilize.
6. Retry the app installation.
   Go to Devices & Groups → [Device Name] → Apps, select Install, and choose the correct app version. Trigger the install only once — issuing multiple install commands immediately after the reboot will recreate the same queue backlog.

Verify: Go to Devices & Groups → [Device Name] → Apps and confirm the app shows a status of Installed with the correct version number. The Activity Feed for the device should show a single successful install event with no subsequent failure entries. This should be visible within 5–10 minutes of triggering the installation.

If this doesn't resolve it

If the Failed To Download error continues after rebooting and retrying, contact Esper Support and include the following:

• Your device ID (found under Devices & Groups → [Device Name] → Device Info)
• The app package name and version number you are trying to install
• The Esper Agent log bundle downloaded in Step 4
• A description of your network environment, including any firewall rules, proxy settings, or CDN restrictions

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.