action stuck at inprogress

expand collapsive

Hello Hexnode Community,

Im totally struggling to manage my iOS devices. I am seeing an issue when I removed the single app kiosk policy from a device. The action seems to be stuck at in-progress state. Neither the device exits from the kiosk nor the remove policy operation is displayed successful. Any solutions? Anyone else had this problem?

action history shows in progress status

All Replies

  • Participant



    Previously, we’ve faced a similar situation. While associating policy with an iOS device, the action was stuck at pending status. Gradually it changed to in-progresss but, the policy was never applied. I’m pretty sure that the device was connected to the network. To check if the device is in sync with the portal, we initiated a scan device action also. But it took more than 2 hours to get the scan device action to be successful. However, with time the policy was also associated. Don’t know what caused the delay. It would be nice to have the solutions discussed here so that we don’t bump into such interventions any more.

  • Hexnode

    Catherine George


    Thanks for the clarifications @Ashton!

    The standard workflow of an iOS device when a policy is pushed from the MDM console is such that:

    1. The server sends a push notification to the device.
    2. The device acknowledges the server and polls for a command.
    3. The device performs the command.
    4. The device reports the result of the last executed command to the server.

    Whenever you push a policy or action from the Hexnode console, the device should acknowledge the Hexnode server. If the device fails to recognize the push notifications, the configurations will not be associated with it. The device acknowledgment is interrupted mainly due to two reasons:

    1. The device is passcode-locked.
    2. The device has a push notification pop-up prompted on its screen.

    In either case, the device will be unable to respond to the server. And, the action shows an In progress status on the Action History page of the device.

    To overcome it, make sure the device is unlocked. Then, if any push notifications permission pops up on the device for any specific app, respond to it or dismiss it. It will help re-push the action, which in your case, is the policy removal from the device.

    Since you have disassociated a kiosk lockdown policy containing the VPN configuration, removing the policy should possibly exit the device from the kiosk and disconnect the device from the existing VPN successfully.

    @Bradley I guess the same thing troubled you. These workarounds would definitely help you overcome it.

    Catherine George
    Hexnode UEM