What can I do if an Automation Assembler deployment fails

Your deployment request might fail for many reasons. It might be due to network traffic, a lack of resources on the target cloud provider, or a flawed deployment specification. Or, the deployment succeeded, but it does not appear to be working. You can use Automation Assembler to examine your deployment, review any error messages, and determine whether the problem is the environment, the requested workload specification, or something else.

You use this workflow to begin your investigation. The process might reveal that the failure was due to a transient environmental problem. Redeploying the request after verifying the conditions have improved resolves this type of problem. In other cases, your investigation might require you to examine other areas in detail.

As a project member, you can review the request details in Automation Assembler.

Procedure

1. To determine if a request failed, select Resources > Deployments > Deployments and locate the deployment card.
   
   Failed deployments are indicated on the card.
   1. Review the error message.
   2. For more information, click the deployment name for the deployment details.
2. On the deployment details page, click the History tab.
   
   
   
   1. Review the event tree to see where the provisioning process failed. This tree is useful when you modify a deployment, but the change fails.
      The tree also shows when you run deployment actions. You can use the tree troubleshoot failed changes.
   2. The Details provides a more verbose version of the error message.
   3. The request ID specifically identifies each request in the tree. You can use the ID to locate a request in the Infrastructure > Activity > Requests page. You might also use it for billing purposes.
   4. If the requested item was an Automation Assembler cloud template, the link to the right of the message opens Automation Assembler so that you can see the Request Details.
3. The Request Details provides the provisioning workflow for failed components so that you can research the problem.

   The request history is retained for 48 hours.

   View and filter deleted deployment history for up to 90 days after deletion

   
   
   
   1. Review the error message.
   2. You can turn on the Dev mode to switch between the simple provisioning workflow and a more detailed flowchart.
   3. Click the card to review the deployment script.
4. Resolve the errors and redeploy the cloud template.
   The errors might be in the template construction or they might be related to how your infrastructure is configured.

What to do next

When the errors are resolved and the cloud template is deployed, you can see information similar to the following example in the Request Details. To see the request details, select Infrastructure > Activity > Requests.