Android apps stuck at Initiated during Hexnode policy app installSolved

Participant
Discussion
11 hours ago Aug 21, 2026

One Android handheld in our fleet is not installing any of the apps assigned through its Hexnode policy. The device is the same model as our other working devices and is using the same policy. In the Hexnode console, every Install Application action stays at Status = Initiated. I already restarted the device, ran a device scan, and used Scan for Apps, but nothing changed. Has anyone seen app installs get stuck like this on just one Android device?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
53 seconds ago Aug 21, 2026
Marked SolutionPending Review

If the assigned apps remain in the Initiated state only on one Android device, it usually means the install command has been queued but the device has not completed processing it.

A useful first step is to refresh the Google Play Store app data on the affected device, especially if the apps are deployed through Managed Google Play.

From the Hexnode console:

1. Go to Manage.

2. Open the affected device.

3. Navigate to Actions > Clear App Data.

4. Search for Google Play Store.

5. Select it and clear the app data.

6. Wait until the action status shows Success.

7. Run a device scan or allow the device some time to check in again.

After this, check whether the assigned apps start installing. If the device is otherwise online and compliant, this can help clear a stale Play Store state that prevents app installation from progressing.

Regards,

Mary Romero

Save