We pushed some policy changes to around 2,000 devices and after that the Hexnode console became pretty slow. The policy action status was also taking a long time to update and many devices stayed in pending for quite a while.
Is this normal during large deployments or should we be checking something else?
23 Views
This behavior can happen during large-scale deployments.
When changes are pushed to a high number of devices simultaneously, the commands are queued and processed per device. Because of this, policy execution status updates may appear delayed in the console even though devices are already receiving the changes.
We checked internally and there are currently no active queue delays from the server side. Please monitor the deployment once more and verify if the issue still persists.
Best Regards,
Isabel Lora
Hexnode UEM
Saw this a couple of times with larger pushes. The actions usually go through fine, but the status page takes a bit to reflect everything properly when that many devices are involved.
Got it, thanks. We’ll check again with our team and monitor the next rollout.
Don't have an account? Sign up
