Salesforce: Agentforce Performance Degradation: Agentforce
Affected components: Agentforce6 instances
Timeline of updates
- update
At 05:15 UTC on May 13, 2026, a performance degradation began impacting the Data 360 query engine. During this time, some customers may have experienced approximately 60% of requests to Agentforce agents failing to return answers and slow or failed queries with the platform.
At 08:47 UTC, we redeployed an update that reintroduced a missing configuration change, which restored normal performance. Data 360 queries and Agentforce agents are now fully operational, and users can resume interacting with them as expected.
We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
26fe5af8252b19a2…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-05-13 05:15 UTC, resolved after 3.5 h, 1 update(s).
- Title
- Agentforce Performance Degradation: Agentforce
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20004035
Salesforce profileRecent Salesforce incidentsAll outages on May 13, 2026Salesforce in May 2026MarkdownJSON