rewindex

ChangesSalesforceFeature Perf Degradation: Agentforce

Salesforce: Incident updated: Feature Perf Degradation: Agentforce

Incident updateNormal progress (typesafe/jev-1.13-20260917, 100%)Changed status.salesforce.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Salesforce removed; blue is what they added. Muted text is unchanged context.

AddedAffected components#1
Before: not present
After: 85 instances
RemovedAffected components#2
Before: 84 instances
After: removed
AddedUpdateupdate#3
Before: not present
After: We're investigating an issue affecting some Agentforce customers who use large language models hosted by a third-party provider. Affected requests may return errors or fail to complete. Customers in multiple regions may be affected when their requests use the impacted capacity. The issue currently appears limited to models hosted by this provider. We're working with our service provider and reviewing changes to how requests are routed to resolve the issue. We're investigating the issue and will provide an update in 30 minutes, or sooner if we have more information.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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 these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayFriday, October 30Fri, Oct 30

6 incident changes

All Salesforce changesSalesforce profileMarkdownJSON