This release of ThingWorx Software Content Management provides a new Auto-Retry feature. When enabled, this feature allows deployments that have timed out, been interrupted by an Abort action, or failed for other reasons, to be retried. Administrators can specify default settings for auto-retry, including the maximum number of retries per deployment, whether to retry deployments to target devices that are not connected, and the maximum number of target devices for any given deployment. When creating a deployment, users can specify the number of times to retry that deployment if it should not succeed. To monitor deployments that are configured to be retried, users can go to the View Assets for Deployments page, where a table shows current deployments, their status, and, if retry is enabled, the number of retries left and the maximum number of retries configured for each listed deployment. For more information on this feature, see the following topics: