Salesforce: Agentforce Performance Degradation: Agentforce
Affected components: Agentforce197 instances
Timeline of updates
- update
We noted a performance degradation impacting Agentforce services on March 4 at 12:30 UTC. A subset of customers using the Geo-aware GPT 4.1 model may have observed 4xx errors when using Agentforce or Prompt Builder.
We identified the technical trigger as a misconfiguration within our LLM gateways, and implemented a configuration update to resolve the 4xx errors on March 4, at 16:20 UTC.
We will continue to monitor the environment to ensure stability and prevent a recurrence. We will also thoroughly investigate the underlying cause and take any preventive action to avoid a repeat in the future. We apologize for any inconvenience this issue may have caused you and your business.
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
0a486c6ba096aaf2…
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-03-04 12:30 UTC, resolved after 3.8 h, 1 update(s).
- Title
- Agentforce Performance Degradation: Agentforce
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003770
Salesforce profileRecent Salesforce incidentsAll outages on March 4, 2026Salesforce in March 2026MarkdownJSON