Description
A NotNow response is returned when a device is unable to execute a command due to certain conditions. Common scenarios include:
Device Boot:
After a device restart, some commands will not execute until the device has been unlocked for the first time.
During this period, the device may respond with a NotNow status to indicate that retrying the command later may succeed.
Device Sleep or Lid Closed (macOS):
macOS devices may respond with NotNow if the device is connected to a network but is in sleep mode or the lid is shut.
When the server receives a NotNow response, it may:
Stop sending commands temporarily.
Attempt to send another command on the same connection.
The following commands are guaranteed to execute in iOS, and never return NotNow: DeviceInformation, ProfileList, DeviceLock, EraseDevice, ClearPasscode, CertificateList, ProvisioningProfileList, InstalledApplicationList, Restrictions.
Resolving NotNow Responses
To resolve the NotNow response in Jamf School, follow these steps:
Restart the Device:
Restarting the device will force a device check-in and may clear the NotNow status.
Ensure the Device is Unlocked:
Make sure the device is unlocked before prompting it to check in or sending commands.
If needed try sending a 'clear passcode' command from Jamf School to temporarily remove a passcode so the other commands will complete.
Retry Commands:
After completing the steps above, attempt to reissue commands from Jamf School.