Hi @ed_evans,
This can happen when there is a temporary communication delay between the MDM server and Apple Push Notification service during macOS enrollment.
When a Mac is enrolled through the Enrollment URL, Hexnode relies on Apple push notifications to wake the device and process pending MDM commands. If that communication is delayed, installation commands may remain pending, take longer than expected, or fail without returning a specific error code. Once the connection is restored and the device checks in again, the queued commands are processed and the Hexnode portal updates the device status to Success.
If the installation eventually completes and the device shows as successfully enrolled, it usually indicates that the issue was a temporary sync delay rather than a failed policy, app, or enrollment configuration.
Best Regards,
Isabel Lora
Hexnode UEM