iPad kiosk app updates stuck at “Queued at Device End” in HexnodeSolved

Hello @pauel ,

The “Queued at Device End” status means Hexnode UEM has sent the command, but the iOS device has not yet processed it. This can happen when the device is busy, has unstable connectivity, is handling a large app package, or has too many pending install commands.

In this case, the key point is that the app is being deployed through a Required Apps policy. Required Apps continuously evaluates device compliance. If the device still appears to be running an older version because the previous install command has not completed, Hexnode UEM may trigger another install command during the next evaluation cycle. Over time, this can create a backlog of repeated install commands for the same app.

Recommended approach:

1. Pick one or two affected kiosks for testing.
2. Send a Remote Restart action to clear the current device-side queue as much as possible.
3. After the device comes back online, avoid sending repeated install/update actions immediately.
4. Deploy the latest app version as a single app using Install Application remote action, or use an automation configured to execute only once per device if automations are available in your plan.
5. Monitor Action History and the installed app version before sending another command.

For large deployments, avoid pushing repeated bulk commands to devices already showing “Queued at Device End”. Smaller batches are safer, especially for kiosks on constrained networks.

Regards,
Simon Scott
Hexnode UEM

Is there a way to find all devices still running the older app version without opening each kiosk one by one? We need to see which devices are still on older builds and which ones already moved to the latest version.

Yes. You can use the built-in Application report to identify devices by installed app version:

1. Go to Reports.
2. Open Built-in Reports > Application > All applications.
3. Search for the in-house app.
4. Export or review the report to compare the installed versions across devices.
5. Use the report to group devices still on older versions and update them in smaller batches.

This is useful when checking whether only specific kiosk groups are stuck or whether the issue is widespread across all devices.