CRM Analytics Recipes Feature Degradation

As the investigation progressed, the team identified additional Hyperforce cells that were impacted as a result of this incident and have been added to the list of impacted instances.

The Technology team has identified that certain instances were not impacted by this incident and will be removed from further posts.

Upon investigation, the team determined a recent release as the potential trigger of the incident and decided to roll back the change. The rollback is underway and initial reports have indicated positive outcomes. The team initially identified that the scope of the incident is limited to instances across the Hyperforce environment only. However,
after further review and analysis, the team determined additional instances within the Salesforce Core services that received the release within the APAC region were also impacted as a result of the incident.
We have posted a General Message for the same which can be reference here : https://status.salesforce.com/generalmessages/1311

The team remains engaged and continues to roll back the change across all the impacted instances. This is expected to take sometime to complete.
We appreciate your continued patience and will provide an update in 60 minutes or sooner if additional information becomes available.

The Salesforce Technology team is investigating the feature degradation impacting multiple Hyperforce cells. During this time, some users may experience difficulties or failures when attempting to perform certain actions such as running recipes that operate on large amounts of data or running newly created recipes. The team is assessing the full scope of the impact. In parallel, we are exploring multiple paths to quickly resolve the issue.

We are expecting the triage to take some more time as it involves thoroughly reviewing the error logs and additional diagnostic information. We appreciate your continued patience and will provide an update in 60 minutes or sooner if additional information becomes available.

We are continuing to investigate the cause of this issue and have engaged additional engineers.