Hi everyone,
I’m running into an issue where several of my remote actions, specifically Remote Wipes and App Installations, are just sitting in a “Pending” state for hours.
The portal says the command was triggered, but nothing is happening on the device side. Is the Hexnode server lagging, or am I missing something? How can I see exactly what’s holding these up?
15 Views
Hi @richard_hank. A “Pending” status usually doesn’t mean the server is lagging; it means Hexnode has successfully queued the command, but the endpoint (the device) hasn’t acknowledged it yet. Think of it as a text message that was “Sent” but not yet “Delivered“.
To see the forensic details of why a command is stalled:
Go to the Manage tab and select the specific device.
Open the Action History sub-tab.
Use the filter icon under Action Status and select Pending.
Common Culprits for the Bottleneck:
Connectivity: If the device is powered off or in an area with no Wi-Fi/Cellular, the command can’t reach it.
OS Throttling: iOS and Android are aggressive about saving battery. They often “kill” background apps (like the Hexnode agent). If the agent isn’t running, it can’t “hear” the push notification to execute the command.
Expired Certificates: If your APNs certificate (Apple) or VPP token has expired, the communication chain for Apple devices breaks entirely.
That makes sense. I checked the Action History and I see a lot of “Scan Device” actions also sitting in Pending. If the device is definitely online, is there a way to “wake it up”?
If the device is online but ignoring the server, the OS has likely put the Hexnode agent into a “deep sleep.”
The quickest fix is to Foreground the App:
If you have the device in hand (or can call the user), have them open the Hexnode UEM / Hexnode For Work app.
Tap the Sync icon.
Opening the app manually forces the OS to give it priority, allowing it to instantly pull all those “Pending” commands from the server.
Don't have an account? Sign up
