# Salesforce: Feature Perf Degradation: Agentforce

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-08-29 01:00 UTC · Resolved: 2026-09-01 19:01 UTC · Duration: 4 d
- Updates: 9 · Affected components: Agentforce, 234 instances
- [Vendor status page: https://status.salesforce.com/incidents/20004386](https://status.salesforce.com/incidents/20004386)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)

## Timeline of updates

- **update** 2026-09-01 10:36 UTC: We’re investigating an issue affecting customers whose Record-Triggered Flows attempt to call an Agentforce agent is failing. This is impacting ‌all sandbox environments that received the recent release, and our investigation indicates that the release introduced a regression.   We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-01 11:19 UTC: We're pursuing an Emergency Release as a fix forward, and the release will be carried out in phases. We'll provide an update in 30 minutes or sooner if additional information becomes available. Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of this ‌post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- **update** 2026-09-01 12:06 UTC: We're continuing to prepare the Emergency Release with final checks underway. Once ready, the Emergency Release will be rolled out in phases to the impacted environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-01 12:42 UTC: We're continuing to prepare the Emergency Release and complete final checks. Once ready, the full deployment is expected to take several hours, as the Emergency Release will be rolled out in phases to the impacted environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-01 13:46 UTC: We're continuing with the preparation for the Emergency Release and we remain on track with our final checks. Once deployed, the phased rollout to impacted environments is expected to take several hours to complete. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- **update** 2026-09-01 14:51 UTC: Preparing the Emergency Release and completing final checks continues. We have several steps to complete before we can begin deployment across the impacted sandboxes. We estimate the entire process will take several more hours to complete. Customers may still see errors when a Record-Triggered Flow calls an Agentforce agent until deployment completes. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- **update** 2026-09-01 15:50 UTC: We’ve completed the build for the Emergency Release and are validating its effectiveness in resolving the issue. Once we have completed validation, we’ll begin deployment to impacted environments. We’ll provide another update in 2 hours or sooner if additional information becomes available.
- **update** 2026-09-01 17:01 UTC: We’ve successfully validated the Emergency Release in the initial environment, confirming that Record-Triggered Flows calling Agentforce agents are executing as expected without the previously observed errors. We’re now preparing to begin the phased rollout across the remaining impacted environments and will monitor progress as deployment proceeds. We’ll provide another update in 3 hours or sooner if additional information becomes available.
- **update** 2026-09-01 19:15 UTC: The issue affecting Record-Triggered Flows calling Agentforce agents in impacted sandbox environments was resolved as of 19:00 UTC. Following successful validation of the Emergency Release, we completed the phased rollout of the fix across all impacted environments and confirmed service recovery. 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.


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