Hello,
Thanks for reaching out to Hexnode Connect.
Yes, this is the expected behavior within the Hexnode portal. When an automation is re-run, Hexnode acts as a blanket re-trigger and pushes the configured action (in this case, the app installation command) again for all devices currently targeted by that automation’s scope.
Currently, there is no built-in option or toggle to automatically exclude devices with a successful status when re-running an automation. It does not act as a “failed-devices-only” retry.
If you need to avoid pushing the app installation commands to devices that already have it, the most practical workaround is to adjust your target scope manually before triggering the action again.
Recommended Workaround:
- Instead of re-running the original automation against the entire group, identify the specific devices that failed.
- Temporarily narrow the target list (e.g., by selecting those specific devices manually or moving them into a temporary “Retry” device group).
- Execute the deployment specifically against that newly defined, smaller scope.
Summary of Re-run Behavior:
- Re-running targets all devices in the current scope.
- Devices with a successful status are not skipped automatically.
- To retry only failed devices, you must manually narrow the target list before running the action again.
I hope this helps clarify how the automation triggers function. If you find any more issues or need further assistance feel free to reach out.
Best regards,
George,
Hexnode UEM
What's new 
19 Views
