Companies / Salesforce / incidents

Salesforce: Feature Perf Degradation: Core Service

Affected components: Core Service869 instances

Timeline of updates

1. update2026-08-20 13:00 UTC

   We’re investigating a feature degradation impacting Revenue Cloud. Customers may receive 400 errors when performing actions such as quoting, ordering and configuring products. We're continuing to narrow down the scope of impact and will update our messaging to reflect this as we learn more. We're engaging additional teams, and we’ll provide an update in 30 minutes or sooner if additional information becomes available.

2. update2026-08-20 13:08 UTC

   We've identified a recent release which may be the trigger of the issue. We're in the process of rolling back the release on a test instance to see if this resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

3. update2026-08-20 13:30 UTC

   The rollback of the recent release on a test instance is still underway. We're continuing to monitor the progress. If this proves successful, the release will be rolled back in all instances which received it. Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that haven't experienced an impact, and these will no longer receive communications about this incident going forward. 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.

4. update2026-08-20 13:53 UTC

   We’re continuing to monitor the rollback of the recent release on the test instance. In parallel, we are investigating whether there are other actions that can be taken to bring customers out of impact, and additional teams are being engaged. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

5. update2026-08-20 14:06 UTC

   We’re examining whether a separate configuration issue may be the trigger of the issue. The rollback of the recent change is still underway and we're continuing to monitor it’s progress. We've also 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’ll provide an update in 30 minutes or sooner if additional information becomes available.

6. update2026-08-20 14:30 UTC

   We’ve run into issues performing the rollback on test instances and are attempting to workaround these issues. Additional teams have joined the investigation and are analyzing whether their configurations may have resulted in the issue experienced by customers. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

7. update2026-08-20 14:45 UTC

   The rollback of the recent release on a test instance has been completed. However,‌ the issue still persists. We're continuing to work with additional teams to check whether a recent configuration changes may instead be the trigger of the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

8. update2026-08-20 14:54 UTC

   Our investigation has highlighted that a recent configuration change seems to align with the start time of the impact. We're currently focused on testing if reverting the configuration change resolves the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

9. update2026-08-20 15:24 UTC

   We're testing changes to the configuration identified in our investigation to determine whether they restore affected Revenue Cloud functionality. In parallel, we're continuing to investigate other configuration changes that align with the start of the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

10. update2026-08-20 15:51 UTC

    Reverting the configuration change didn't resolve the issue. However, we've identified another recent change that aligns with the start of the impact and are deploying an update on an affected environment to validate whether it restores Revenue Cloud functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available.

11. update2026-08-20 16:18 UTC

    Our investigation has identified a recent deployment to a related service as the likely trigger of the Revenue Cloud issue. We're preparing changes to restore the previous configuration across affected environments and are validating the remediation approach before proceeding. We'll provide an update in 30 minutes or sooner if additional information becomes available.

12. update2026-08-20 16:51 UTC

    We've successfully validated a configuration change that resolved the errors affecting Revenue Cloud functionality in a test environment. We're now applying this change across the remaining affected environments, with recovery progressing as the remediation is completed. We'll provide an update in 30 minutes or sooner if additional information becomes available.

13. update2026-08-20 17:26 UTC

    The configuration change we validated is restoring Revenue Cloud functionality, and we’ve now applied the remediation across multiple affected environments. We’re continuing remediation efforts across the remaining environments while monitoring recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.

14. update2026-08-20 18:02 UTC

    We’ve applied the remediation across the affected environments, and monitoring indicates that Revenue Cloud functionality is returning to normal. Customers may begin to see functionality restored and improvements in their experience as the remediation takes effect. We’re completing remediation in additional environments as a precautionary measure and continuing to monitor and validate recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.

15. update2026-08-20 18:17 UTC

    We’ve resolved the issue affecting Revenue Cloud. We applied the remediation across affected environments, restoring functionality for customers who experienced 400 errors when performing actions such as quoting, ordering, and configuring products. 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.

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