Editing and retiring deployments

In CloudRadial AutomationAI you can edit a deployment to re-pin it to a different published version or runner, and retire it when it should no longer accept runs. This article covers both, including the impact of retiring a workflow's last active deployment. It is for Admin and Owner roles.

• Editing a Deployment
• Retiring a Deployment
• What Retiring Affects

Editing a Deployment

Open Deployments and click Edit on a deployment, or click its row, to open the edit dialog. You can change:

• Published version — re-pin the deployment to a different published release version of the same workflow
• Runner — move the deployment to a different active runner

Future runs use the version and runner you select. Save is enabled once at least one of the two differs from the current binding. The environment label is fixed for the life of the deployment and is not changed here. Because a workflow has one active deployment at a time, editing the existing deployment is how you change the version or runner a workflow uses without retiring it.

Retiring a Deployment

Retiring stops a deployment accepting new runs. Open the deployment and choose Retire; AutomationAI confirms before applying it. Retiring is permanent and cannot be undone — to run the workflow again afterward you create a new deployment. The retired deployment drops out of the active Deployments list.

What Retiring Affects

Scheduling depends on an active deployment, because a Routine runs the deployed version. If the deployment you retire is the workflow's last active deployment, retiring it permanently deletes that workflow's scheduled tasks, which removes its Routine. Before you confirm, AutomationAI checks the impact and warns you, showing how many scheduled tasks would be deleted; if that count is non-zero, this is the workflow's last active deployment. This deletion cannot be undone, so if the schedule still matters, deploy the workflow again and recreate the schedule on its Properties page.