Performance Degradation

The permanent fix has been completed, and teams are in the final testing phase. Once testing is concluded, the fix will be deployed to all affected Sandbox instances.

We will provide the next update upon the completion of the fix deployment or sooner if more information becomes available.

The Technology team is still working on the long-term fix that will be deployed for all impacted instances and will have an update by 2300 UTC. The quick fix was successful for customers who reported the issue.

We will provide an update in 4 hours or sooner if additional information becomes available.

The Technology team continues to work on the long-term fix that will take approximately 4 hours. The quick fix is ready for the customers who have reported the issue.

We will provide an update in 60 minutes or sooner if additional information becomes available.

The Technology team is currently working on a long-term fix and it is estimated to take 2-3 hours to complete. The team has also identified a quick fix to bring customers out of impact by making org-specific changes. The investigation showed that there is an underlying platform actions issue and a code change (a gate change) will be deployed to fix this issue.

The rollback did not mitigate the issue and customers are still impacted.

We will provide an update in 60 minutes or sooner if additional information becomes available.

The rollback of the recent change is still in progress. Engineers are also exploring multiple paths to resolution.

We will provide an update in 60 minutes or sooner if additional information becomes available.

After further investigation, the Technology team has determined that the emergency release after the main release is the potential trigger of this issue. The team is working on rolling back the change on one sandbox to see if it mitigates the issue. Engineers are continuing to troubleshoot the issue.

We will provide an update in 60 minutes or sooner if additional information becomes available.

The Salesforce Technology team are continuing their investigation into this issue and are exploring multiple paths to resolution.

We will provide an update in 60 minutes or sooner if additional information becomes available.

Following further investigation into this issue, it has been confirmed that this is only impacting sandboxes for a subset of Salesforce customers. Engineers are continuing to troubleshoot the issue.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

After further investigation it has been determined that a subset of customers on an additional instance, USA668S, are also experiencing this issue. Our engineering team is continuing with their work to troubleshoot the issue.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

The Salesforce Technology team are continuing their investigation into this issue, which is only impacting a small subset of customers on CS111 and CS112. Additional teams are assisting to understand the cause of the issue. Initial investigations indicate that this may be a result of a recent release.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.

At 13:00 UTC, on Jan 7, 2024, the Salesforce Technology team became aware of an issue impacting a subset of customers on CS111 and CS112. Some customers may receive an error message when attempting to click on records in Salesforce Lightning. The error will read “"SyntaxError: Bad control character in string literal in JSON at position 72(line 1 column 73)”. Our team is actively investigating this issue and have engaged additional teams to assist.

We’ll provide an update in 60 minutes or sooner if additional information becomes available.