Delivery Target States during Deployments
When a package is deployed to an asset, the state of an asset changes through the deployment. Depending on whether you have deployed a file-based package or an instruction-based package to an asset, the states differ.
 |
These states track the state of an asset through the deployment, and not the overall status of the deployment.
|
The following image depicts the states that a delivery target goes through for the deployment of a file-based package:
The following image depicts the states that a delivery target goes through for the deployment of an instruction-based package:
The following table provides information about the delivery target states:
State | Description | ||
|---|---|---|---|
Created | Once the deployment is saved, the state of the target asset is “created”. | ||
Pending | Every 30 seconds, the ThingWorx Platform searches for deployments that are in the “created” state and moves them to the “pending” state. It also checks all the assets that are associated with the deployment. | ||
Ineligible | If the target asset for deployment does not meet the criteria for a package, it goes to the “ineligible” state. | ||
Notifying
| If the value of the maxConcurrentUpdates property is not exceeded and the target device can handle more deployments than it is currently processing, the deployment moves from the “pending” state to the “notifying” state. If the edge device does not respond within a specified time, the deployment moves to the “aborted” state. If the notification fails for any other reason, it moves to the “failed” state. | ||
Notified
| When the edge device receives a message about the deployment and responds to the server, the state changes to “notified”. | ||
Scheduled
| When the server receives the response from the edge device, the state changes to “scheduled”. | ||
Downloading
| The state changes to “downloading” when the package is being downloaded to the edge device. | ||
Downloaded
| When the package is successfully downloaded to the edge device and is waiting to be installed, the state changes to “downloaded”. | ||
Sending Instructions
| When the package instructions are being sent to the edge device, the state changes from “pending” to “sending instructions”. | ||
Instructions Received
| When the edge device receives the instructions and the device sends a response to the server, the state changes to “instructions received”. | ||
Installing | When the package is being installed on the edge device, the state changes to “installing”. | ||
Completed | When the edge device finishes installing the package successfully, the state changes to “completed”. | ||
Abort Pending | When the edge device is unable to download the package and a time-out is pending, the state changes to “abort pending”. | ||
Cancel Pending | When a user cancels the deployment, the state changes to “cancel pending”. | ||
Failed | When the package is not downloaded to the edge device or if the edge device is unable to install the package, the state changes to “failed”. | ||
Aborted | If a time-out occurs during the “notifying” or “downloading” state, then the state changes to “aborted”. | ||
Canceled by User | If the user aborts the deployment, then the state changes to the “Canceled by User” state. | ||
Pending Retry | This delivery state becomes available only if auto-retry feature is enabled. For more information, see How Auto-Retry Works. | ||
Retrying | This delivery state becomes available only if auto-retry feature is enabled. For more information, see How Auto-Retry Works. |