Companies / Salesforce / incidents

Salesforce: Feature Perf Degradation: Core Service

Affected components: Core Service7 instances

Timeline of updates

1. update2025-10-03 16:41 UTC

   We’ve identified a Salesforce feature degradation in which Omni-Channel Studio is not loading for a subset of customers with custom Lightning Web Components. We’re investigating the issue and will provide an update in 30 minutes or sooner if we have more information.

2. update2025-10-03 17:19 UTC

   We rolled back a recent release as this was the suspected trigger, but it did not resolve the issue. We are actively investigating the issue, exploring multiple paths to resolution, and assessing whether the impact may be related to other recent changes. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

3. update2025-10-03 19:51 UTC

   Our telemetry indicates that customers on instances GBR44S, CS240, CS260, CS242 are out of impact following the release rollback. CAN2S and CS345 remain in impact as Salesforce teams continue to troubleshoot these instances. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

4. update2025-10-03 20:20 UTC

   Further investigations found that USA946S was not affected by this incident. We apologize for the inconvenience this has caused.

5. update2025-10-03 22:35 UTC

   Instances GBR44S, CS240, CS260, and CS242 remain out of impact following the release rollback. CAN2S and CS345 remain impacted, and we will implement a fix for these instances following the major release this weekend. We’ll provide an update after the release and fix are deployed. We apologize for any impact this issue is having on your business.

6. update2025-10-04 10:52 UTC

   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. update2025-10-04 14:04 UTC

   The fix was successfully deployed on GBR100 and GBR44s and they are out of impact now. These instances have been removed from this post to more accurately reflect the impact radius.

8. update2025-10-04 16:48 UTC

   The fix was successfully deployed on USA664S, and is out of impact now. This instance has been removed from this post to more accurately reflect the impact radius.

9. update2025-10-04 21:10 UTC

   The fix was successfully deployed on SWE82, and it’s now out of impact. This instance has been removed from this post to more accurately reflect the impact radius.

10. update2025-10-04 21:38 UTC

    Investigations have revealed that EU50 was also impacted by this incident. The fix has been successfully deployed, and EU50 is now out of impact. This instance has been removed from this post to more accurately reflect the impact radius.

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