# Salesforce: Feature Perf Degradation: Agentforce

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-09-06 16:30 UTC · Resolved: 2026-09-07 00:15 UTC · Duration: 7.8 h
- Updates: 6 · Affected components: Agentforce, 36 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004423](https://status.salesforce.com/incidents/20004423)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-09-08 20:28 UTC: We’re investigating an issue affecting Agentforce session scoring and tagging functionality for a subset of customers. Our teams are actively working to identify the trigger and restore service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-08 20:58 UTC: We’re continuing to investigate an issue affecting Agentforce session scoring and tagging for a subset of customers. Our teams are analyzing processing failures and reviewing affected customer environments to determine the trigger and identify a path to restore functionality. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-08 21:37 UTC: Our teams have narrowed the investigation to failures occurring during session processing and are working to identify a path to restore functionality. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- **update** 2026-09-08 22:41 UTC: We have identified a potential fix and are preparing to apply it to affected customer environments. We’ll monitor session tagging performance following the change to determine whether functionality recovers while our investigation into the underlying issue continues. We’ll provide another update as significant progress is made.
- **update** 2026-09-08 23:24 UTC: As of 23:02 UTC, September 8, we resolved the issue affecting Agentforce session scoring and tagging for a subset of customers. Session scoring and tagging functionality is now operating at usual performance levels.  This is the final update for this incident. We apologize for any inconvenience for our customers.
- **update** 2026-09-09 00:55 UTC: Upon further investigation, we've determined that the start and end 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.


---
Canonical: https://rewindex.com/company/salesforce/incidents/20004423 · Markdown: https://rewindex.com/company/salesforce/incidents/20004423.md · JSON: https://rewindex.com/api/v1/companies/salesforce/incidents/20004423 · Generated 2026-10-18T10:29:20.026Z