Devices stuck on “Scanning in progress” / policies pending for daysSolved

Participant
Discussion
4 weeks ago Sep 23, 2026

Hi Hexnode team,

We’ve been seeing a similar issue to the one discussed here:

Device scan stuck on "scanning in progress" and policy actions remain "initiated" after bulk push

The main difference is that we’re enrolling our devices one by one, not doing a large bulk push, so there shouldn’t be a large command queue involved.

Some newly enrolled devices remain stuck on “Scanning in progress”, while others have policies showing as “Pending” for days. Manual syncs complete successfully on the device side, but the portal status doesn’t seem to move forward.

So far, I’ve tried:

Manual sync
Rebooting the devices
Re-enrolling the affected devices

The issue still comes back on some devices.

Are there any other server-side, enrollment, or command-processing issues that could cause this when bulk queueing isn’t a factor? Is there anything specific we should check in the portal or device logs?

Thanks!

Replies (1)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 23, 2026
Marked SolutionPending Review

Hi @shan_deluxe,

Since bulk queuing isn’t a factor here while enrolling your Apple TV devices, this issue usually happens when background push notifications fail, a policy hits a blocked dependency, or server tokens are out of sync. Here are the main areas to check in your portal and device setup:

1. Apple Push Notification Service (APNs)

In Hexnode UEM portal, navigate to Admin > APNs. Verify that the APNs certificate is active and hasn’t expired. If it was renewed using a different Apple ID, server-to-device push commands will fail.

2. Policy Dependencies & Conflicts

  • Blocked Payloads: If a policy status stays “Pending”, check if a specific payload inside the policy is failing—such as an app with no available VPP/Apple Business licenses, an enterprise Wi-Fi profile, or an unreachable certificate (SCEP/CA) server.
  • Overlapping Policies: Ensure the device isn’t assigned multiple conflicting policies with opposing settings.

3. Device Date & Time

Ensure the device clock is set automatically. Incorrect date or time breaks secure SSL communication with the MDM server.

4. Apple Business Token Sync

In the Hexnode UEM portal, navigate to Admin > Apple Business/School Manager > Automated Device Enrollment. Under Accounts, locate your account and verify that the server token status is active and has not expired. If it has expired, download a fresh server token from Apple Business and update it here. For detailed steps refer to our help documentation on How to assign ADE devices to Hexnode?.

If these configurations are verified and newly enrolled devices still freeze, contact Hexnode Support (support@hexnode.com) for further assistance. with the affected device serial numbers to clear any stuck token queues on the backend.

Regards,
Isabel Lora
Hexnode UEM

Save