This usually happens when the Hexnode MDM app itself is added as one of the “allowed apps” in a multi-app kiosk.
The main point is that the Hexnode app isn’t just another app. It’s the one that actually runs the kiosk in the background. When you add it to the allowed list, the device tries to launch the same app that’s already controlling kiosk mode. That can cause conflicts, and over time it may crash or stop responding.
So here’s what you need to do:
That alone usually fixes the stability issue.
If you need access to device info or messages in kiosk don’t add the Hexnode app icon to the kiosk screen. Instead, use Peripheral Settings.
Peripheral Settings let you:
This gives you what you need without launching the Hexnode app itself, so the kiosk engine can keep running normally.