Task status
The following table explains the task status shown on the Task view and Task archive pages.
Every status is associated with a color code that indicates the status category.
| Color code | Status | Description |
|---|---|---|
| Accepted | Task has been created. | |
| Delayed | Sophos Mobile waits for other tasks to complete before it starts the task. | |
| Will be retried | Sophos Mobile can’t connect to a third-party server, for example a push notification or mail server. Sophos Mobile retries the task every three minutes. The task fails after five attempts, that is, after 15 minutes in total. | |
| Started | Task has been started. | |
| In progress | Execution of the task is being prepared. | |
| Task bundle in progress | Execution of the task bundle is being prepared. | |
| Notified | The Sophos Mobile Control app was notified. The task fails if the app doesn’t respond within 72 hours. | |
| Commands sent | Sophos Mobile has sent the task to the Sophos Mobile Control app. The task fails if the app doesn’t acknowledge receipt of the task within 15 minutes. | |
| Result evaluation started | The Sophos Mobile Control app has received the task and processes it. The task fails if the app doesn’t report success within 15 minutes. | |
| Result incomplete | Result evaluation showed that not all commands’ results have been received by now. | |
| Waiting for user interaction | There is a pending user action on the device. The task fails if the user doesn’t react within 72 hours. | |
| Waiting for task completion | An installation task was sent to the device, but it may take some time to complete. | |
| Device is locked | Task waits for the device to become unlocked (iOS). The task fails if the user doesn’t unlock the device within 72 hours. | |
| Successful | Package has been installed or the commands have been successfully executed. For the initial provisioning of the Sophos Mobile Control app the task must finish with status Installed. | |
| Installed | The Sophos Mobile Control app has been installed successfully. The device is provisioned now. | |
| Result evaluation failed | Result evaluation could not be executed. | |
| Task partly failed | Not all commands of the task could be executed successfully. | |
| Failed (retry queued) | Task has failed and will be retried later. | |
| Task failed | Task has failed and no further retries are queued. | |
| Completely failed | Task has failed, and it is not possible to retry it. | |
| Not started | Task is part of a task bundle and was not processed yet. | |
| Skipped | Task is skipped because it’s not supported by the device. | |
| Unknown | The server has no information about the task status. |
Color codes
| Color code | Category |
|---|---|
| Open | |
| In progress | |
| Success | |
| Failure | |
| Other |