# Salesforce: Mule Soft Performance Degradation: APIDesigner, APIFunctional Monitoring, Runtime Fabric +2 more

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-05-16 09:30 UTC · Resolved: 2026-05-16 15:52 UTC · Duration: 6.4 h
- Updates: 5 · Affected components: APIDesigner, APIFunctional Monitoring, Runtime Fabric, Runtime Manager, Secrets Manager, 5 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004023](https://status.salesforce.com/incidents/20004023)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-05-16 12:59 UTC: At 09:30 UTC, May 16, 2026, we identified a performance degradation affecting the Secrets Manager Provider and API in our production environment. As a result, customers attempting to deploy or restart applications may be unable to do so successfully, as secrets cannot be retrieved during this process.  Currently running applications that are not restarting are not impacted and will continue to operate normally. We have identified a potential technical trigger and have initiated a remediation process.  We are working to restore full service and will provide an update within 30 minutes or sooner if additional information becomes available.
- **update** 2026-05-16 13:28 UTC: The previous attempt to restore the service didn't yield the desired results. We continue to investigate the issue and analyze data to determine the best path to resolution. We’ll provide an update upon significant update, or sooner if additional information becomes available.
- **update** 2026-05-16 14:34 UTC: We are working on resolving the impact on runtime manager in the US control plane. Hybrid on-prem customers using customers using Application Manager will not be able to deploy or re-deploy their applications. We’ll provide an update upon significant update, or sooner if additional information becomes available.
- **update** 2026-05-16 15:58 UTC: We have successfully validated and tested the fix. Initial reports have indicated positive results and services were restored to normal operating levels for the verification instances. We are reviewing additional logs to confirm the fix. We’ll provide an update upon significant update, or sooner if additional information becomes available.
- **update** 2026-05-16 16:29 UTC: The issue affecting MuleSoft Runtime Manager for Hybrid Standalone (HSA) deployments, where some applications became stuck in a transition state (e.g., "Deploying" or "Starting"), has been resolved. We have mitigated the underlying issue, and system telemetry indicates that platform stability and status reporting have returned to normal. \#\#\# Required Customer Action While the core system issue is resolved, applications that became stuck during the incident window may not automatically return to an active state. Action Required: If your application is still showing a stuck status, please manually restart or redeploy the application to force a state synchronization and restore normal operation. We sincerely apologize for the disruption this caused to your deployment operations. A full Root Cause Analysis (RCA) will be conducted and shared in accordance with our standard processes.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004023 · Markdown: https://rewindex.com/company/salesforce/incidents/20004023.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004023 · Generated 2026-10-18T10:29:33.768Z