Android file deployment stalls or misses files after bulk policy associationSolved

Hello @sutton ,

Scan Device is not designed to perform a full file-level audit for every file deployed through file management policies. It refreshes device information and compliance-related details, but it does not currently validate each deployed content file or trigger installation of missing files.

For Android file deployment issues where downloads fail or stall, use the following approach:

1. Update Hexnode for Work to the latest available version. Recent builds include improvements to automatically retry file downloads that fail due to unstable connectivity.
2. After updating, confirm that the Hexnode for Work app update shows Success in Action History.
3. Keep the device online and allow the retry cycle to complete. The retry mechanism can run within a 24-hour window; it is not necessarily delayed until the end of 24 hours.
4. If files remain missing and you need to force a fresh evaluation immediately, re-push the affected file management policy. This can be done by making a minor edit and saving the policy, or by disassociating and re-associating the policy.
5. For large content deployments, especially with thousands of files or multiple devices in parallel, deploy in smaller batches where possible and ensure the devices have a stable network connection.

If the portal shows apps as missing even though they are installed and working on the device, that is usually a device-to-portal inventory sync mismatch. Running a device/app scan or restarting the device and scanning again can refresh the app inventory.

Regards,
Simon Scott
Hexnode UEM