Salesforce incident
We're continuing to address an issue impacting Anypoint Runtime Manager for CloudHub 2.0 customers. We've identified the underlying trigger — a recent change to the Runtime Manager UI — and a rollback
Salesforce experienced a minor incident on June 23, 2026 affecting RUNTIMEPLANE-CA and RUNTIMEPLANE-EU and 1 more component, lasting 1h 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 23, 2026, 02:38 AM UTC
Degradation Started: muleSoftFeatureDegradation
- monitoring Jun 23, 2026, 02:40 AM UTC
We're aware of an issue impacting Runtime Manager for MuleSoft Anypoint Platform CloudHub 2.0 customers. Customers attempting to change their Mule runtime version via the Runtime Manager UI are finding the change appears to succeed, but actually does not, and it reverts to the previous version. Some customers may also encounter an error when attempting to update. We are working on a workaround and will publish this as soon as it is available. We're working to restore full functionality as quickly as possible and will provide an update in 60 minutes, or sooner if additional information becomes available.
- monitoring Jun 23, 2026, 03:18 AM UTC
We're continuing to investigate the issue impacting Runtime Manager for MuleSoft Anypoint Platform CloudHub 2.0 customers. We've identified a configuration change which we believe is the likely trigger of the issue and are now working to roll back this change. The rollback is underway and is estimated to take approximately two hours to complete. We will then undertake a period of monitoring to validate performance. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 23, 2026, 03:39 AM UTC
We're continuing to address an issue impacting Anypoint Runtime Manager for CloudHub 2.0 customers. We've identified the underlying trigger — a recent change to the Runtime Manager UI — and a rollback of this change is currently underway. The rollback is estimated to take approximately two hours to complete. A workaround is available. Please visit our Known Issue article here, http://sfdc.co/WEHv3 for guidance on steps you can take while we complete the rollback. We'll provide an update in 60 minutes, or sooner if additional information becomes available.