Feature Degradation

We are working to remove the faulty patch release from the repository. Once this has been done, the rollback will be attempted again. This is expected to take some time to complete.

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

The lock has not been successful in preventing the redeployment of the latest version of the patch. We are investigating other options to bring affected customers out of impact.

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

The lock has been put in place to prevent the latest version of the patch from being automatically redeployed. We are validating whether this action has been successful.

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

Attempts to roll back to the previous version were unsuccessful, as each time they were attempted, the latest version was redeployed. We are in the process of putting a lock in place that will prevent the latest version of the patch from being redeployed when a rollback is attempted.

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

Investigations have pointed to a recent patch release being the potential trigger. We have paused the rollout of the recent patch release to additional instances while we investigate. Additional teams have been engaged to assist.

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

We’re investigating an issue affecting Salesforce CRM Analytics (CRMA) dashboards. Some users may experience intermittent failures when trying to use dashboards or find that previously viewed dashboards are either unavailable or showing outdated data. Report creation and modification remain unaffected.

This issue only impacts customers using a CRMA license. We’ve tried to mitigate the impact by rolling back some instances to a previous stable version. However, rolling back some of the impacted instances hasn't been possible.

We are continuing to troubleshoot and are exploring alternative solutions to resolve the issue. We’ll provide an update in 30 minutes or sooner if additional information becomes available.