Automation script stuck in In Progress state after device disenrollmentSolved

Once an automation action such as script execution has already been pushed to a device, it cannot be canceled from the Hexnode portal if it has moved to the In Progress or Running state.

Automation action statuses work as follows:

• Pending: The action has not yet reached the device. It can be removed or deleted safely.
• In Progress / Running: The action has already been delivered to the device and is executing at the OS level. Hexnode cannot remotely stop or delete the action at this stage.

If you do not want the automation to trigger again for other devices, you can pause it from Automation > select the active automation > Actions > Pause. This prevents further runs but does not cancel an action that is already running on a device.

In this case the device that shows In Progress was already disenrolled. It was enrolled again later. Would the old running status still block the automation?

If the device was disenrolled, the previous device record may still appear in the portal history. You can clear the old disenrolled device record by marking it as disenrolled from the Disenrolled Devices report.

Go to Reports > Disenrolled Devices, open the affected device entry, then use Actions > Mark as Disenrolled.

This does not cancel a script that had already reached the device, but it helps clean up the stale device record associated with the old enrollment. If the device has been enrolled again, it will be treated as a separate managed device record for future automation runs.