How to fix ACSF site domains stuck on "update" environment

Issue

In rare cases, after a failed code deployment, some site domains can remain with the "update" environment, instead of the "production" environment.

Resolution

In the situation where a code deployment has failed, and site domains remain associated to the "update" environment, this can be resolved by applying the steps outlined below.
These steps assume that the deployment failure is due to a platform issue and not due to code itself.
Essentially these steps will perform a redeployment of currently deployed code which will correct those site domains that are incorrectly associated with the "update" environment.

Steps to rectify

• Go to the "Update code" page
  • From the menu, select "Site Factory" and then "Site Update"
  • This should direct you to the path admin/gardens/site-update of your Site Factory dashboard
     
• From within the "Start Update" tab on the page
  • Leave the "Scope" setting as default ("Sites")
  • Leave the "Start time" setting as default ("Immediately")
  • Under the "Site update action"
    • Set the "Choose a path to deploy..." to be the same as "Currently deployed" - that is the path that is already deployed
    • Select the "Code only" option
    • If this is a production environment then select the checkbox for "Select this check box to confirm that you want to update your public-facing production environment."
       

Once the settings have been chosen, click on the "UPDATE" button to start the deployment for the "production" environment.