rewindex

ChangesSalesforceFeature Perf Degradation: Agentforce, Core Service

Salesforce: Incident updated: Feature Perf Degradation: Agentforce, Core Service

Incident updateNormal progress (rule, 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.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-21 02:07 UTC
AddedUpdateupdate#3
Before: not present
After: We're aware of an issue impacting Agentforce Coworker. A subset of customers may experience intermittent request failures, and conversations may stop partway through an answer without an error message. We engaged the third-party service provider, and we're seeing error rates decrease. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
AddedUpdateupdate#4
Before: not present
After: Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
AddedUpdateupdate#5
Before: not present
After: Agentforce Coworker is now operating at normal service levels. Requests are completing successfully again. Error rates returned to normal after a third-party service provider recovered their services. 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.

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.

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

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

YesterdayWednesday, October 21Wed, Oct 21

1 incident change

All Salesforce changesSalesforce profileMarkdownJSON