macOS patch enforcement stuck when multiple Enforce Patch Deadline policies overlapSolved

Participant
Discussion
4 hours ago Nov 16, 2026

Has anyone seen Hexnode macOS patch enforcement get stuck with Declarative Device Management errors? A few Macs are not enforcing scheduled macOS updates. Action History shows the update commands as Failed or Pending, with an error like: Activation “com.hexnode.ddm.activation.status:<token>” has errors. The affected Macs have Declarative Device Management activated, the Bootstrap Token is escrowed, and there is plenty of free disk space. Manual installation works, but enforcement through Hexnode does not seem to trigger reliably.

Replies (1)

Marked SolutionPending Review
Hexnode Expert
9 minutes ago Nov 16, 2026
Marked SolutionPending Review

This error usually points to a failure in Apple’s Declarative Device Management software update flow rather than a standard app deployment failure.

Since DDM is activated, the Bootstrap Token is escrowed, and disk space is sufficient, check whether the macOS software update process or the Hexnode agent reporting process is stalled.

Useful checks/workarounds:

1.Restart the macOS software update daemon:

sudo killall softwareupdated

2. If OS version reporting or scan actions are also delayed, identify the Hexnode agent daemon label:

sudo launchctl list | grep -i hexnode

3. If the Hexnode agent service appears, restart it using the exact label shown. For example:

sudo launchctl kickstart -k system/com.hexnode.hexnodeagentd

4. After that, run a device scan or trigger a manual sync from the Hexnode UEM app.

If the issue continues across multiple patch versions, also review whether more than one Enforce Patch Deadline action is being applied to the same Mac at the same time.

Regards,
Mary Romero

Save