Salesforce incident
We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health m
Salesforce experienced a minor incident on June 17, 2026 affecting BRA14 and BRA16 and 1 more component, lasting 1h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 17, 2026, 10:50 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 17, 2026, 10:55 PM UTC
We're aware of an issue impacting Agentforce. A subset of customers may encounter a "Something went wrong, please try again" error when accessing Agentforce across multiple instances. We're actively investigating potential triggers. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 11:32 PM UTC
We continue to investigate this issue. We have deployed a fix on one of the impacted instances and are currently monitoring performance. If successfully validated, we will deploy the fix to all impacted instances to restore services as quickly as possible for customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 11:59 PM UTC
We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health metrics across instances that have received the fix so far. We'll provide an update in 30 minutes or sooner if additional information becomes available.