- Introduction
- Managing solution projects and packages
- Managing solution deployments
- Best practices
Deployment statuses
Deployment and operation status details available in the Solutions view in Automation Cloud.
The Solutions view provides you with various details such as:
- For solutions packages: name, latest version, description, author, and publish date.
- For deployments: operation, status, version, location, and timing information (for example, start and end time).
- For the deployment history of a package: version, operation, status, timestamp, and author.
Note the following about the Deployments table:
- In the Deployments table, column names and their order are designed to distinguish between deployment operations and their outcomes, and to reduce ambiguity between deployment state and operation state.
- Operation statuses are displayed as text values. Select the filter icon above the table to filter deployments by one or multiple operation statuses at the same time.
- The Last operation column indicates the most recent operation performed on the deployment.
- The operation status and the time the operation ran also appear in the Last operation cell (for example,
Install · Successful · 1 day ago). Possible operation statuses are Draft, Successful, Failed, In progress, and Failed rollback. - Columns are ordered to reflect their relationships. Name, Status, and Version appear one next to each other, while Last operation reflects the status and details of the operation, not of the deployment itself.
Operation statuses
The following table describes the possible statuses of your deployment.
| Operation | Operation status | Description |
|---|---|---|
| Install | Draft | You saved your solution deployment as a draft and can now resume or discard the installation. |
| Successful | You installed a solution package. | |
| Failed | The installation failed. You can retry the installation. | |
| Failed rollback | Rollback failed, but some components were already deployed. Make sure to manually clean up any partially installed solution components before trying to deploy the solution again. | |
| In progress | The installation operation is in progress. | |
| Change version | Draft | The version change was saved as a draft. You can resume or discard the version change. |
| Successful | The version change was successful. This applies to both upgrades and downgrades. | |
| Failed | The version change failed. You can retry the operation. | |
| Failed rollback | The rollback operation failed. | |
| In progress | The version change is in progress. | |
| Edit configuration | Draft | The configuration change was saved as a draft. You can resume or discard the change. |
| Successful | You successfully edited a solution deployment. | |
| Failed | The configuration change failed. You can retry editing the solution deployment. | |
| Failed rollback | The rollback operation failed. | |
| In progress | The configuration change is in progress. | |
| Uninstall | Successful | You successfully uninstalled a deployment. |
| Failed | Uninstalling a deployment failed. | |
| In progress | Uninstalling a deployment is in progress. | |
| Activation setup | Draft | Activation setup has either not started or is not complete. The Status column shows Inactive (Needs setup to activate). |
| In progress | Activation setup is ongoing. | |
| Successful | Activation setup completed. The Status column may show either Active or Inactive (Ready to activate). | |
| Failed | Activation setup failed. The Status column may show Inactive (Failed activation). |
Rollback is not an action you can select, because when an install, a version change, or a configuration change fails, Solutions runs a rollback automatically to restore the previous state. If the rollback also fails, the operation status is Failed rollback, and the deployment offers the Review errors and Retry rollback actions.
Last operation for deployments with activation
When you install or upgrade a solution with the Activate option enabled, the Last operation column reflects the outcome based on whether activation setup is resolved in the same session as the deployment.
| Scenario | Last operation |
|---|---|
| Activation completes successfully | Install (or Change version) · Successful |
| Activation setup is required; you fix the connections and complete activation in the same session | Install (or Change version) · Successful |
| Activation setup is required; you close the session before completing activation | Install (or Change version) · Successful; the Status column shows Inactive. After you complete the activation setup, the last operation updates to Activation setup · Successful. |
| You deploy with Activate immediately turned off, then activate later from Inactive (Ready to activate) | Install · Successful. The last operation does not change to Activation setup. |
Version display by operation
For deployments with a status of Draft, the row menu shows only Continue editing and Delete draft. This lets you continue or discard the saved operation.
The following table describes how deployment operations affect the installed package version and, where applicable, a target package version. In the Deployments table, this information is displayed in a single Version column.
When a newer package version is available for a deployment, the Deployments table shows an Upgrade icon 
directly in the Version column.
| Operation and status | Version |
|---|---|
| Draft | The version that is pending installation. |
| Install successful | Installed version |
| Upgrade failed | The version for which you initiate the upgrade. You can retry deployment, or uninstall the package. |
| Rollback failed | The version for which the upgrade is intended. You can retry deployment. |
| Rollback successful | The version for which the rollback is performed. You can uninstall the package or upgrade to a different version. |
| Activation setup | Can display the currently installed version and the version for which the upgrade is intended. |
Allowed operations by status
The following table describes the deployment transition status and allowed user operations for each status:
Legend:
✅ - Available
❌ - Not available
| Operation status | Status column | Install | Activate | Upgrade | Uninstall | Delete |
|---|---|---|---|---|---|---|
| Draft | - | ✅ | ❌ | ❌ | ❌ | ✅ |
| In progress | - | ❌ | ❌ | ❌ | ❌ | ❌ |
| Failed | - | ✅ (retry installing the deployment) | ❌ | ❌ | ❌ | ✅ |
| Successful | Active | ❌ | ❌ | ✅ | ✅ | ❌ |
| Successful | Inactive (Ready to activate) | ❌ (activate the deployment first) | ✅ | ✅ | ✅ | ❌ |
| Successful | Inactive (Needs setup to activate) | ❌ (activate the deployment first) | ❌ | ❌ | ✅ | ❌ |
| Failed | Inactive (Activation failed) | ❌ | ✅ (retry activating the deployment) | ❌ | ✅ | ❌ |