## TL;DR
A remote lock stuck on pending means the device has not checked in with Jamf: it is offline, push notifications are broken, or the MDM profile is damaged. Confirm the device's last check-in, verify Apple push is working, then try again or fall back to other controls.

## The query
```text
jamf remote lock command stuck on pending: what to do
```

## Use this when
- remote lock command sits on pending in Jamf
- lost device needs locking urgently
- lock works on some devices but not one

## Not for
- devices that never enrolled in Jamf
- wipe commands (different command, same debugging)
- Android devices (different MDM flow)

## Steps
1. In Jamf, check the device's last check-in time and last inventory update. Expected output: you know how long the device has been silent
2. Confirm the device is online: ask the user or check network logs. Expected output: connectivity confirmed or ruled out
3. Verify Apple Push Notification service is reachable and the Jamf push certificate is valid. Expected output: push path healthy
4. Cancel the stuck command and reissue the remote lock. Expected output: a fresh command queued
5. If it still pends, check the MDM profile on the device is intact; re-enroll if damaged. Expected output: profile healthy or re-enrolled
6. If the device stays offline, document the pending lock and use your lost-device procedure for the interim. Expected output: risk documented and the ticket tracked

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qLqxp4G2TaWsKobk5eQzHA