---
title: "Troubleshooting Kandji Agent Check-In"
slug: "troubleshooting-kandji-agent-check-in"
updated: 2025-06-10T13:52:26Z
published: 2025-06-10T13:52:26Z
canonical: "support.kandji.io/troubleshooting-kandji-agent-check-in"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.kandji.io/kb/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Kandji Agent Check-In

macOS devices enrolled in Kandji attempt to check in every 15 minutes. If a device isn't checking in, try the following quick fixes to regain communication between Kandji and the Mac.

### Check Internet Connectivity

- Ensure the device has an active internet connection with access to the domains and ports outlined in our [Using Kandji on Enterprise Networks](/v1/docs/using-kandji-on-enterprise-networks) support article. As a troubleshooting step, try a different connection, like a mobile hotspot, to rule out the internet connection as the reason.

### Force a Check-in

#### Self Service

- The **Sync** button in the Device Info section of Self Service allows end users to easily initiate device check-ins when requested by their IT administrators. ![](https://cdn.document360.io/0844b095-d720-4a7b-bb17-ec97d9bc6e41/Images/Documentation/Kandji-Support-KB-1024AM@.png)

#### Command Line

- Force Kandji to run via the command line. Enter the following command in Terminal.app to force Kandji to check-in. The Terminal output may provide additional details about why the Kandji agent isn't checking in as expected.

```bash
sudo kandji run -F
```

### Reinstall the Kandji Agent

- If the last MDM check-in is recent, initiate a Reinstall Agent MDM command from the Device Action Menu in Kandji. The command's status can be monitored from the Device Record's activity tab by looking for the completion of the `InstallEnterpriseApplication` command. ![](https://cdn.document360.io/0844b095-d720-4a7b-bb17-ec97d9bc6e41/Images/Documentation/ryxnoaqdqgvtr06jcqzhtuqughthpia5jq.png)
- If the InstallEnterpriseApplication command returns a status of **Not Now (device is busy)**, ensure that the Mac has a user logged in and is plugged into a power source, then initiate the command again. More information on handling NotNow status responses can be found in [Apple's Developer Documentation](https://developer.apple.com/documentation/devicemanagement/implementing_device_management/handling_notnow_status_responses).

### Restart

- If a process has stalled, restarting the device may resolve the issue and help the device start checking in normally. Kandji can wait up to 30 minutes to check in after a restart to ensure the device is not occupied with updates or other activities.

### Re-enroll

- Manually re-enrolling the problem device may resolve any check-in-related issues.
- Ensure the correct Blueprint is selected when enrolling a device. If a different Blueprint is selected, the device will enforce that Blueprint's assigned Library items and parameters. The device record will not be duplicated after re-enrolling. Kandji will link the new enrollment with the existing device record.