Is Salesforce down?

Degradation Started: featurePerfDegradation

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.

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.

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.

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.

Degradation Started: featureServiceDisruption

We're aware of the issue affecting credit card transactions on Commerce Cloud, where customers are unable to complete purchases using credit cards at checkout. We're restarting the affected applications to restore transaction processing and working on a broader fix to resolve this for all impacted customers. 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 the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.

We've applied manual fixes across all known affected environments to restore credit card transaction processing on Commerce Cloud checkouts. We're now testing an automated, fleet-wide fix to fully resolve this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Degradation Started: agentforcePerformanceDegradation

The Salesforce Technology team has identified a potential trigger for the issue and is working on implementing a fix to resolve it. Thank you for your patience as we work to resolve this issue.

Degradation Started: featureServiceDisruption

We're investigating an issue impacting Revenue Cloud that's preventing some customers from adding new products and saving quotes, and blocking checkout. Investigations indicate the issue is due to a recent release. We're working to resolve the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate the issue preventing customers from adding new products and saving quotes in Revenue Cloud. We've engaged multiple teams and are working on a fix-forward to resolve the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Investigations have highlighted that the impact radius is narrower than initially understood. We've confirmed that GovCloud instances aren't impacted and we'll now remove these instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward: USA9002, USA9004S, USA9008, USA9010S, USA9014, USA9016S, USA9020, USA9022S, USA9026, USA9402, USA9404S, USA9902, and USA9918S. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Customers attempting to add new products or save quotes may continue to see incomplete results. We're reviewing the changes introduced in the release and testing a fix to confirm if it resolves the issue. Our investigations indicate that an update to a component in the release is the likely trigger. We've engaged additional teams to support the investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate the issue preventing customers from adding new products and saving quotes in Revenue Cloud. Affected customers can view existing quotes and can create new quotes, but can’t add or edit products on either new or existing quotes. This occurs only when the constraint feature is enabled. We're pursuing two paths to resolution: a fix-forward and reverting only the specific change causing the issue, while preserving other important fixes included in the release. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate the issue in Revenue Cloud where customers can't add or edit products on either new or existing quotes when the constraint feature is enabled. We've identified the specific change we believe caused this issue. We're testing an undo of that change on a test instance to confirm it resolves the problem before considering a wider fix. In parallel, we're preparing an alternative code fix as another path to resolution. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've reproduced the issue preventing customers from adding products in Revenue Cloud and have confirmed the specific change causing it. We're preparing a fix that undoes this change. We're running verification checks and will test the fix before applying it to the live environment. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

We've submitted code fixes to undo the specific change in Revenue Cloud that causes the issue when adding new products and saving quotes. We expect this to be applied to the live environment in about one hour, and to the patch version in about three hours. As a temporary workaround, disabling the constraint feature allows customers to continue adding new products, though this may not work for every configuration. We'll provide an update in 30 minutes, or sooner if additional information becomes available.

We've confirmed that undoing the change fixes this Revenue Cloud issue with adding products on quotes, in our tests. We've also found that a broader set of affected versions needs the same fix. We're preparing additional fixes to cover these, and the release is now estimated to take three to four hours, followed by testing in a testing instance before we roll it out more broadly. We'll provide an update within the hour or sooner if additional information becomes available.

We're continuing to work on fixes for the Revenue Cloud issue that prevents adding new products and saving quotes, and we've confirmed that release 264 is not impacted. Work continues on the fix for the earlier affected release. As a workaround, turning off the constraint feature allows affected customers to add products again, though this may not work for every customer's setup. We'll provide an update within the hour or sooner if additional information becomes available.

We're currently testing the fix to resolve the issue that prevents Revenue Cloud customers from adding new products and saving quotes. This is expected to take a few hours to complete. We'll provide an update in 4 hours or sooner if additional information becomes available. If testing is successful, we'll roll out the fix across all affected environments.

We've validated the fix and are now rolling it out to all affected customers in phases. As we deliver the fix to each instance, affected customers will see functionality return to normal. Because of this phased approach, resolution times may vary by customer. We’ll provide updates on ‌specific resolution times as this information becomes available. We anticipate that the full rollout of the fix will take some time. We’ll provide an update in 4 hours or sooner as additional information is available.

We're continuing to roll out the fix to all impacted instances. As we're rolling out the fix in a phased approach, customers will notice restored functionality at different times. So we can confirm the exact restoration time for each instance, we'll follow up with a separate notification as the deployment of the fix completes.

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.

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. We anticipate that the full rollout of the fix will take some time. We’ll provide an update once the rollout has completed, sooner as additional information becomes available.

Disruption Started: serviceDisruption

We isolated the issue and are working to find the best path to resolution. We will provide an update in 30 minutes or sooner if we have more information.