API reference: Document what we know about "NotNow" (#39412)

- Document what we know about "NotNow"
- Context:
https://fleetdm.slack.com/archives/C050XE4CQNA/p1770244126667719?thread_ts=1769555555.606569&cid=C050XE4CQNA

---------

Co-authored-by: Rachael Shaw <r@rachael.wtf>
This commit is contained in:
Noah Talerman
2026-02-13 17:45:41 -06:00
committed by GitHub
co-authored by Rachael Shaw
parent 8c33922230
commit 5430f8760f
+1 -1
View File
@@ -7334,7 +7334,7 @@ This endpoint returns the results for a specific custom MDM command.
In the response, the possible `status` values for macOS, iOS, and iPadOS hosts are the following:
* Pending: the command has yet to run on the host. The host will run the command the next time it comes online.
* NotNow: the host responded with "NotNow" status via the MDM protocol: the host received the command, but couldnt execute it. The host will try to run the command the next time it comes online.
* NotNow: the host acknowledged the MDM command but couldnt run for one of [Apple's documented reasons](https://developer.apple.com/documentation/devicemanagement/handling-notnow-status-responses#Handle-NotNow-Responses). Per Apple, the host retries automatically. Apple doesnt specify when the retries happen, or whether they depend on clearing _all_ blocking reasons or just one.
* Acknowledged: the host responded with "Acknowledged" status via the MDM protocol: the host processed the command successfully.
* Error: the host responded with "Error" status via the MDM protocol: an error occurred. Run the `fleetctl get mdm-command-results --id=<insert-command-id` to view the error.
* CommandFormatError: the host responded with "CommandFormatError" status via the MDM protocol: a protocol error occurred, which can result from a malformed command. Run the `fleetctl get mdm-command-results --id=<insert-command-id` to view the error.