From 5430f8760f1839cac693fd68c7b84733bd24f976 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Fri, 13 Feb 2026 18:45:41 -0500 Subject: [PATCH] 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 --- docs/REST API/rest-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/REST API/rest-api.md b/docs/REST API/rest-api.md index 1a05cbadcc..3ff494fcdc 100644 --- a/docs/REST API/rest-api.md +++ b/docs/REST API/rest-api.md @@ -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 couldn’t execute it. The host will try to run the command the next time it comes online. +* NotNow: the host acknowledged the MDM command but couldn’t 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 doesn’t 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=