Device action execution states and offline behavior

  • Release version: Australia
  • Updated May 20, 2026
  • 1 minute to read

    • Execution state codes for device actions and how the platform handles actions triggered on offline devices.

    Table 1. Action execution state codes
    State Code Description
    Running 602 Action is currently executing. Also applies to actions queued for execution on an offline device.
    Declined 605 The end user declined the confirmation prompt without running the action.
    Closed successful 606 Action completed successfully.
    Closed unsuccessful 607 Action completed but the remediation failed. Review the linked task record for failure details.

    Device actions on offline devices

    When a device action is triggered on an offline device, the platform queues the action and retries it automatically when the device reconnects. Queued actions are valid for one calendar day. If the device does not reconnect before the end of the calendar day, the action must be triggered again.

    When the device is offline, the interface indicates that the action could not be completed immediately. The end user receives a notification when the queued action executes.

    Queued actions remain in Running state until the device reconnects and the action completes or fails.

    Note:
    The platform processes queued actions in batches of 200, with a 10-second delay between batches.