Windows automation cannot be paused or deleted in HexnodeSolved

Participant
Discussion
3 days ago Nov 18, 2026

We have a Windows automation in Hexnode that we need to stop immediately. It was tied to a PowerShell script/action that caused multiple Windows devices to reboot repeatedly, and remote shell was not working on some affected machines.

The problem is that the automation itself cannot be paused, archived, or deleted. Each attempt fails with an internal platform error. We were able to edit the automation action, but not stop or remove the automation.

Has anyone seen this behavior before? What is the safest way to prevent the automation from triggering more disruptive actions while waiting to regain control of pause/delete?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
3 days ago Nov 18, 2026
Marked SolutionPending Review

Hi @ezekiel , Welcome to the Hexnode Community.

If a Windows automation cannot be paused or deleted but the action inside the automation can still be edited, the safest immediate mitigation is to replace the disruptive action with a harmless one.

In this case, changing the automation action from Restart to Scan Device is the recommended temporary workaround. The Scan Device action only refreshes basic device details such as check-in status, battery, and storage information. It does not reboot the device or execute a script.

After applying that workaround, review any associated custom script configuration and remove or disable the script from any other active policies or automations where possible.

If pause/delete still fails with an internal platform error, try the following after the fix is available:

  1. Log out of the Hexnode UEM portal.
  2. Log back in to refresh the active session.
  3. Go to Automation > select the active automation > Actions > Pause.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
3 days ago Nov 18, 2026
Marked SolutionPending Review

We changed the action to Scan Device and that stopped the reboot behavior from continuing. Pause and delete still failed at first, though. We were worried about machines where the script might have been queued but not run yet.

Marked SolutionPending Review
Hexnode Expert
3 days ago Nov 18, 2026
Marked SolutionPending Review

For queued or pending script execution, replacing the automation action with a safe action helps prevent the automation from continuing to trigger the previous disruptive action. However, devices that already received or executed the command must still be checked and remediated separately.

Also note that scripts executed through Hexnode are not stored on the endpoint as reusable inventory files by Hexnode UEM, and deleted script content cannot be recovered from the portal after removal. If the script file exists separately on a device, it would need to be recovered from that device directly.

Regards,
Isabel Lora
Hexnode UEM

Save