macOS update deadline automation not triggering in HexnodeSolved

Hi @v_collins,

For macOS update deadline automations, the first things to verify are whether the automation actually triggered and whether Hexnode generated the OS update command for the device.

Check the following:

1. Open the automation and confirm that it is active and not paused.
2. Review the automation activity feed to confirm whether the automation was triggered for the target device or group.
3. Go to the affected device in Manage and check Action History.
   • If the automation successfully pushed the OS update command, you should see an action such as Update OS.
   • If Update OS is missing, the automation may not have delivered the update action to the device.
4. On the device page, open Patches and Updates and review:
   • Applicable patches
   • Enforced patches
5. If the patch information looks outdated, run Actions > Updates > Scan for Updates and wait until the scan succeeds. Then check the Patches and Updates tab again.

If the automation was paused or did not trigger for the device group, enable it and re-trigger it using Once ASAP for testing. Once it triggers correctly, the managed macOS update notification should appear on the device and the update enforcement action should be visible in the Action History.

Best Regards,
Isabel Lora
Hexnode UEM

I had a similar case where the automation looked configured correctly, but it had been paused earlier while testing. The device group was fine, but nothing was being sent until the automation was enabled again. Checking the activity feed made it obvious because there were no recent trigger entries.

That seems to match what I’m seeing. The device gets the broadcast message, but the update itself isn’t enforced. If I re-trigger the automation as Once ASAP, does it stack another update command or replace the previous one?

Re-triggering the macOS update automation does not stack multiple separate deadline configurations for the same device. The newly triggered command applies the latest automation configuration and can replace the previous pending command.

For testing, use this sequence:

1. Confirm the automation is active.
2. Run Scan for Updates on the test Mac.
3. Verify the required macOS update appears under Applicable Patches.
4. Trigger the automation using Once ASAP.
5. Check the automation Activity Feed and the device Action History.
6. Confirm that the managed update notification appears on the Mac.

Also note that if an end user cancels or postpones the macOS update prompt, enforcement may appear delayed during testing. Hexnode can re-push the update based on the configured deadline behavior, but user interaction on the device can affect what you observe immediately after the trigger.

Best Regards,
Isabel Lora
Hexnode UEM