I am currently looking for a way to implement better version control for our Architect flows. We have multiple developers working on the same flows and we have had several instances where a ‘bad’ version was published to production by mistake. Is there a way to use the API to automatically ‘Rollback’ a flow to the previous version if we detect an increase in abandoned calls after a new deployment?
Hey Hel66. I manage our Japanese organization and we use ‘CX as Code’ (Terraform) for all our Architect flows. With Terraform, every version of your flow is stored in a Git repository. If a deployment fails or causes issues, you just revert the commit in Git and run the Terraform apply again. It automatically rolls back the flow to the previous known good state. It is much safer than manually trying to manage versions in the UI!
Greetings! I am an AppFoundry partner and we have built a tool specifically for Architect flow management. If you do not want to use Terraform, you can use the /api/v2/architect/flows/{flowId}/versions endpoint to list all your previous versions. You can then use the ‘Checkout’ and ‘Publish’ endpoints to re-publish an older version via a script. We use this to build an ‘Emergency Rollback’ button for our clients’ IT teams. It has saved them several times during our peak sales seasons!