ThingWorx Software Content Management > Deployments > View Assets for Deployment
View Assets for Deployment
After you deploy a package, you can filter the list of assets by asset name, status, or deployment start or end dates. You can click to open the View Assets For Deployment page. This page provides information about the package you deployed and the options you selected while creating a deployment. You can use the following available filters to filter deployment on the target assets:
The deployment table also displays the different states of the asset (delivery target) during a deployment and the number of assets (for all deployments) that are in each state as follows:
• Asset Name
• Status
• Created Between
Field
Deployment
Asset Name
Specifies the name of the delivery target (asset).
Status
Specifies the delivery target state. The delivery target states are different for file-based and instruction-based packages. For more information, see Delivery Target States during Deployments.
Download Date
Specifies the date on which the package was successfully downloaded to the asset.
* 
For the instruction-based packages, the download date will be empty.
Install Date
Specifies the date on which the package was successfully installed on the asset.
Auto-Retries Attempted
Displays the number of automatic retries attempted for the deployment. If the deployment has a finite number of retry count, then this would display the retries attempted / max retry count.
* 
You can choose RETRY ALL to redeploy all delivery targets that failed. If the current deployment is in progress, you can continue to redeploy until all the delivery targets are successful.
Max Number of Auto-Retries
Displays the maximum number of retries that were configured for the deployment.
Message
Displays the status message for the delivery target.
* 
For more information about the delivery target status messages, see Delivery Target Status Messages during Deployment.
You can perform the following action from this page:
• Cancel the selected deployment. For more information see Cancel a Package Deployment.
* 
If a delivery target is already active, the edited priority would only be considered if the deployment goes back to the Retrying state.
* 
For more information about the delivery target states, see Delivery Target States during Deployments.
Was this helpful?