Retry a failed launch

An Auto Scaling Group whose first launch fails stays in your list as Failed, with the reason on its details page. Retry Launch stops what is left of the launch, removes whatever it created, and launches the group again from its saved settings.

Before you begin

• A group that failed on its first launch and shows Failed.
• Permission to update VMs in the project. See TIR Access Control.

For any other Failed group, contact support with the group name.

Find out why the launch failed

On the Auto Scaling Groups list, select the group’s name. The details page shows the reason and a hint for the cause:

• Configuration rejected: contact support with the group name.
• Too little capacity in the region: retry later, or start with fewer VMs.
• Credit too low: add credit, or start with fewer VMs.
• A temporary fault: retry.

A failed launch removes the VMs it had created.

Retry the launch

Select Retry Launch on the details page, or in the group’s row menu on the list. The group launches again with its current Minimum VMs and Maximum VMs, and keeps its SSH keys and security group. The group keeps its own copy of the plan, disk size and SSH keys, so a retry works even when the source VM has been deleted.

TIR first cleans up the previous attempt, and the group is Creating until all its first VMs are ready. If the retry fails to start, TIR gives the reason. See Create an Auto Scaling Group for the steps.

When the failure repeats

The details page offers Delete Auto Scaling Group. To start again with different settings, delete the group and create a new one. See Delete an Auto Scaling Group and Create an Auto Scaling Group.

To ask support for help, see Create a support ticket. Have the group name ready. For other messages, see Troubleshooting TIR Auto Scaling Groups.