"Failed to sync" alert for Apple MDM Management — how to verify and resolve

iOS

When the Esper Console displays a "failed to sync" alert under Apple MDM Management, your iOS devices may still be fully managed and responsive. In many cases the alert clears automatically before any action is needed.

Why this happens

The Esper iOS MDM integration syncs periodically with Apple Push Notification service (APNs) and Apple Business Manager (ABM) or Apple School Manager (ASM). Brief network interruptions, Apple server latency, or a delayed Console UI refresh can trigger a "failed to sync" alert that resolves on its own once the next sync cycle completes. The alert does not always mean device management has stopped working.

Step 1 — Check whether the alert has already cleared

1. Open the Esper Console and navigate to Devices & Groups.
2. Locate the affected iOS device or device group.
3. Review the Apple MDM Management sync status shown on the device detail panel.
4. If the status now shows as synced, the transient error has resolved and no further action is needed.
5. If the status still shows as failed, hard-refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on macOS) before continuing — the Console can display a stale failed state after the underlying sync has already recovered.

Step 2 — Confirm device management is still working

1. In Devices & Groups, select an affected device and attempt to push a management command — for example, a policy update via Apps & Configuration.
2. Check the Activity Feed for the device to confirm the command was received and acknowledged. This distinguishes a genuine sync failure from a UI display issue.

Step 3 — Troubleshoot a persistent sync failure

If the "failed to sync" alert persists across multiple sync cycles and device management commands are not being received, work through the following checks in order.

1. Navigate to your Apple MDM settings in the Esper Console and verify that your ABM or ASM credentials are valid and have not expired.
2. Check the expiry date of your MDM push certificate. Push certificates expire annually — if the certificate has expired, MDM communication stops entirely. An expired certificate cannot be renewed transparently; devices must be re-enrolled and re-supervised, which removes existing MDM profiles.
3. Confirm that APNs connectivity is available from your network. Apple publishes its APNs IP ranges and required ports; blocks at the firewall level will prevent MDM commands from being delivered even when credentials are valid.
4. Take a screenshot of the error state in the Console, including any error codes or timestamps displayed, to support further investigation.

Verify: After completing the checks above, all affected iOS devices should show an active synced state in Devices & Groups, with no pending or failed sync indicators, and management commands should be acknowledged in the Activity Feed within one full sync cycle.

If this doesn't resolve it

If the sync status remains failed after completing all steps, or if device management commands are confirmed not reaching devices, contact Esper Support. Include the following when you reach out:

• A screenshot of the failed sync state, including any error codes and timestamps
• The expiry status of your MDM push certificate
• Confirmation of whether management commands are failing or only the UI alert is affected
• The number of devices impacted and whether the failure is limited to a specific group

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.