--- schema_version: "1" id: afd84ad6ea264277db8f29dc2b371629e0afade767ace0fab3c43eddec1a5f54 title: Updating Apps Deployed to CloudHub 2.0 collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub-2/ch2-update-apps.md canonical_url: https://docs.mulesoft.com/cloudhub-2/ch2-update-apps source_site: docs.mulesoft.com content_type: documentation content_hash: 86171271bd5d08833b4d6fee39f1e6086f395a3934ad4a22e88e21b3bf59a2e4 description: MuleSoft Documentation Site latest: true --- --- product: CloudHub 2.0 --- # Updating Apps Deployed to CloudHub 2.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When deploying an application to CloudHub 2.0, Runtime Manager automatically versions and creates a new _configuration_. Application configurations enable you to: - View the configuration change history of the application. - Roll back the configurations to an earlier version if the currently applied configuration has issues or is unstable. - View the application status. Possible values are: Running At least one replica is receiving traffic (Started state). Not running None of the replicas are receiving traffic. Unknown The target is disconnected. When this value appears, there is a MuleSoft-related outage or incident. - Make updates to a deployed application’s configuration, including: - Application file - Application deployment package version - Deployment target settings, such as runtime version, number of replicas, and whether the application is running in cluster mode - Endpoint and TLS settings - Resource allocations, including CPU and memory - App property values - View logs and diagnostics associated with a configuration. ## Update App Settings 1. From Anypoint Platform, select **Runtime Manager** > **Applications**. 2. Click the app name. 3. In the navigation menu, click **Settings**. 4. Click **Configuration** to display the app configuration history: Config changes tab Shows the changes to the successfully deployed application configuration and includes the last 10 configuration deployments in order by configuration creation date. A unique hash identifies each configuration in the history. All changes tab Shows a history of versions created from the configuration deployment and the actions performed on each version. 5. Depending on the deployment target (shared or private space), change the deployed configuration: - Specify runtime options, such as uploading a new application file or changing the deployment target and resource allocation. - View the app’s current version. - Change the endpoint for the app. - Change app behavior with properties. - Disable or enable app logs and specify log levels. 6. Click **Apply Changes**. A message appears at the top of the page indicating the configuration is in progress. 7. Click **View status** to view the [status](#replica-statuses) for each replica in the deployment. When the configuration is successfully applied and deployed, a message appears at the top of the page, with application status, configuration identifier, completed date, and replica status. The new configuration appears in the **Config changes** list. If the configuration updates fail to deploy, the message indicates that CloudHub 2.0 didn’t apply the configuration, the configuration status is `Update failed`, and the configuration appears in the **Config changes** history without a label. In failure cases, the deployment attempts to roll back to the last successful version of the configuration. In some situations, the rollback might not succeed, and the configuration status is `Update failed`. ## Replica Statuses Started The replica is receiving traffic. Pending The replica is waiting to start. Starting The replica is starting. Deleting The deletion of the replica is in progress. Deleted The replica was deleted. Stopping The replica is stopping. Stopped The replica has stopped (it is not receiving traffic). Failed The configuration failed to deploy. Recovering: The replica is attempting to restart after terminating. The last successfully deployed configuration is retained until the new (desired) configuration is successfully deployed. Applying The previous configuration of the replica is running, and new configuration settings are in the process of being implemented. You can configure a _desired state_ that indicates your ideal state of the replica. For example, if you expect the replica to be running, you can set the desired state to `running`. ## Rolling Update vs. Recreate Deployment Model Depending on the deployment model, CloudHub 2.0 applies new configurations as either: - Rolling updates Maintain availability by incrementally updating replicas. This model means zero downtime while CloudHub 2.0 applies updates to the application. Because CloudHub 2.0 applies updates as rolling updates, different application versions run simultaneously until the update completes. For this reason, ensure that your applications can run multiple versions in parallel. - Recreate Terminate replicas before redeployment. Redeployment is quicker and doesn’t require additional resources. ## Roll Back to a Previous Successful Configuration If a deployed configuration has issues, you can roll back to a previous successful version of the configuration. > [!NOTE] If this is the first deployment of the application, the rollback version isn’t defined. In > case of a failed deployment, the application remains in the failed status. 1. From Anypoint Platform, select **Runtime Manager** > **Applications**. 2. Click the app name. 3. In the navigation menu, click **Settings**. 4. Click **Configuration** to display the app configuration history. 5. Select the version to which to roll back from the **Config changes** history. To change the runtime version of a previously used configuration, select the desired version from the **Runtime Version** dropdown list. You can change any other configuration before deploying. 6. Click **Deploy**. The configuration moves to the top of the **Config changes** history list and displays the new deployment date, and it retains its original identifying hash. > [!NOTE] After End of Extended Support for Mule runtime 4.3 and 4.4, Mule applications deployed to > CloudHub or CloudHub 2.0 environments are stopped. ## See Also - [Deploying Apps to Shared Spaces](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-shared-space) - [Deploying Apps to Private Spaces](https://docs.mulesoft.com/cloudhub-2/ch2-deploy-private-space) - [Changing App Behavior with Properties](https://docs.mulesoft.com/cloudhub-2/ch2-manage-props) - [Viewing Log Data for Deployed Apps](https://docs.mulesoft.com/cloudhub-2/ch2-view-logs) - [Generating Apps Diagnostics and Analyzing with Einstein](https://docs.mulesoft.com/cloudhub-2/ch2-view-diag) - [Managing App Schedules](https://docs.mulesoft.com/cloudhub-2/ch2-manage-schedules)