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?