Script action fails in Hexnode Action History after appearing successfulSolved

Participant
Discussion
4 weeks ago Sep 28, 2026

I’m trying to run a script from Hexnode that should move devices as part of our workflow. At first, it looked like the script action was successful, but I couldn’t find the devices where I expected them to be moved.

After checking the device under Manage > Action History, the script entry shows as failed with a red info icon. I tried running it again, but the same issue keeps happening. Does this mean Hexnode is not running the script correctly, or is the problem with the script itself?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 28, 2026
Marked SolutionPending Review

Hello @luke ,

If the Action History entry shows failed, the script was not executed successfully on the device, even if the action initially appeared to be queued or sent.

Hexnode UEM remotely enforces the script on the device OS, but the script content itself is created and maintained by the admin. If there is a syntax issue, invalid command, wrong path, missing permission, unsupported operation, or platform mismatch in the script, the device can return a failure.

A good way to confirm this is:

  1. Open the affected device in Manage.
  2. Go to Action History.
  3. Check the script execution entry.
  4. Hover over or open the red info icon to view the failure reason.
  5. Run the same script manually on a test device with equivalent permissions.
  6. Fix any script-side errors and then execute it again from Hexnode.

If the script does not run successfully when executed manually on the device, it will also fail when pushed through Hexnode.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
4 weeks ago Sep 28, 2026
Marked SolutionPending Review

Okayy, now I got it. I wasn’t able to get the script to run manually either, so it sounds like the issue is with the script. I’ll try to correct it and run again from Hexnode.

Save