Search

Companies / Salesforce / incidents

Salesforce: Feature Perf Degradation: Agentforce

Impact: minorStatus: resolvedStarted Resolved (14 d)8 updatesSource: status.salesforce.com (opens in new tab)

Affected components: Agentforce21 instances

Timeline of updates

  1. update

    At 11:53 UTC, on March 17, 2026, a feature degradation began impacting the Agentforce Data Library service. During this time, some customers may be unable to create new Agentforce Data Libraries. This issue does not impact previously created data libraries, which continue to function as expected. We're exploring multiple paths to isolate the underlying cause of the issue and implement a fix to restore the services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  2. update

    We have identified a potential triggering event related to a recently enabled feature. We are currently evaluating whether temporarily turning off this feature will safely resolve the issue. In parallel, we are continuing our investigation by reviewing logs and analyzing recent changes. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. update

    Upon further investigation, the Salesforce Technology team has determined that the start time of impact is different than initially understood. We have now 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.

  4. update

    Our investigation continues, and multiple potential root causes have been identified, with several active swimlanes in play. We are analyzing the logs to help with the investigation. An Emergency Release (ERR) is being considered, with preparations underway. We are also working on disabling the feature gate as a short-term solution. We are testing a workaround for users and if successful, will create a Known Issue article that we will post to Trust once it is available. We'll provide an update once additional information becomes available.

  5. update

    We are actively working on a fix-forward implementation to address this issue. Once tested and validated, this will be deployed to all impacted instances. Timing is expected to be Thursday, March 19 for the fix-forward rollout to complete. In the short-term, we have a Known Issue article to help inform users, available here: http://sfdc.co/bBeg9Q. We’ll provide an update once we have been able to validate the fix-forward and the rollout has begun. We apologize for any inconvenience this issue is causing to customers.

  6. update

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  7. update

    This Trust post has been updated to include additional cells that may also be affected by this issue. We expect the fix-forward rollout to begin within the next 24 hours, and will be undertaken in a staggered approach, outside of regional core business hours. We’ll provide an update once the fix-forward rollout is underway. We apologize for any inconvenience this issue is causing to customers.

  8. update

    After evaluating our initial mitigation strategy, we determined that turning off a recent feature change was the most effective path to a stable resolution. As of 19:25 UTC, March 19, 2026, this change has been deployed across the fleet, and customers should no longer experience issues creating new Agentforce Data Libraries. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab). Salesforce profile · Recent Salesforce incidents · Markdown · JSON