Actions stuck in Not now

Actions for iOS devices are not processed and remain in the Actions tab with a state such as Push sent, Delivered or Not now.

Actions are commands that Relution executes on enrolled devices. These can be triggered either implicitly by a policy configuration or explicitly by applying an action. An overview of all pending and executed actions can be found in device details under the Actions tab.

See also: Device does not communicate with Relution → — it covers expired certificates and other server-side causes.


Device has been restarted

  • The device has been restarted and has not yet been unlocked
    • The digital keychain is locked until a device is unlocked for the first time after a restart. As a result, the operating system cannot yet access stored passwords and therefore cannot connect to an encrypted Wi-Fi network

Action in the User channel

  • The action was sent on the user channel and no user is currently signed in on the device

Device has connection status Not Now

In some cases, iOS/iPadOS devices respond to commands from the MDM server with Not Now. This always happens when the device is not ready to communicate with the MDM server at that moment.

There are various reasons that can lead to a Not Now response. The following list contains the triggers currently known and is not exhaustive.

  • The device is locked / user interaction is required
    • Some commands cannot be executed while the device is locked, including
      • Applying certain restrictions
      • Configuring a Wi-Fi connection
      • Installing or updating apps
      • Installing certificates that require user consent
  • Network or battery status
    • The device has too low a battery level to start the process
    • The device’s network connection is unstable
  • User delays software updates
    • An update is to be scheduled (ScheduleOSUpdate or InstallLater) and the user explicitly delays the update
  • The device is not yet fully enrolled
    • Some commands can only be executed after the device has completed Automated Device Enrollment (ADE, DEP in the portal) and/or the supervision process
  • The device is otherwise busy
    • The system is currently performing a critical task (update, iCloud backup, or restore)

Solution

  • Unlocking the devices and establishing a stable Wi-Fi connection
  • Logging in to the device with a user account, if necessary
  • Confirming any dialog boxes from the operating system
  • Charging the device beforehand, if necessary

Actions that should no longer be executed can be selected in the device details under the Actions tab and canceled with Cancel actions. This is possible for actions in the Pending, Push sent and Not now states; actions in the Delivered state can no longer be canceled. Enable lost mode and Disable lost mode cannot be canceled in the Push sent state either.


Further information

The Not Now status is normal behavior of iOS/iPadOS and is not specific to Relution.

Since version 5.8.1, Relution is able to understand Not Now responses from devices. If a device responds to a command with Not Now, Relution changes the connection status for that device in the inventory accordingly. In the device list, the status is shown in the Connection state column; the corresponding filter lists all devices with the status Not Now. In addition, the affected action receives the state Not now in the Actions tab. When the device checks in again, Relution sends the action once more; it then shows Delivered again until the device executes it or responds with Not Now once more. To get devices in this state to communicate with the MDM again, they usually need to be unlocked and any pending operating system updates need to be performed, for example.

Some actions, such as Enable lost mode and Reset lock passcode, are prioritized by the device and accepted even in this state. Since version 5.9, Relution also treats these actions as a priority: they are sent to the device before all other pending actions. The remaining actions are not discarded; they stay open and are sent afterwards. This ensures that devices that previously responded to actions with Not Now can still be put into Lost Mode or that a forgotten passcode can still be changed. Relution also prioritizes the actions Disable lost mode, Locate device, Alert, Wipe device and Enterprise Wipe.

Apple developer documentation on the NotNow status →

How helpful was this article?