Service Disruption

The team has determined that the best path forward is to disable, recompile, and re-enable the instance to bring it out of impact. This set of actions is currently underway, and confidence is high that this process will resolve the issue.

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

The restart process was completed; however, this did not achieve the desired results and further actions are required. The team has identified an alternative path forward and is moving forward with this.

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

The team continues to perform all required actions to complete the restart process.

We don’t have an estimated time for when this will complete; however, we’ll provide an update in 45 minutes or sooner if additional information becomes available.

The team continues to perform all required actions to complete the restart process.

We don’t have an estimated time for when this will complete; however, we’ll provide an update in 30 minutes or sooner if additional information becomes available.

The restart process was started at approximately 07:17 UTC. In tandem, the team continues to explore alternative paths to resolution should this action not achieve the desired results.

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

A number of potential triggers have been ruled out and the team continue to investigate, including reviewing any changes which may be contributing to the issue. Additional resources have been engaged to assist with this. The team is also exploring the option of starting database and app tier restarts to try alleviate impact.

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

The team has determined that impact levels are more significant then initially understood and have revised the impact level to service disruption. Multiple resolution options are still being considered and the team is working diligently to determine the best path forward.

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

The Salesforce Technology team continues to investigate the issue to determine the likely trigger and best path to resolution. All potential paths are being explored.

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

We are investigating a potential cause of the issue.

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

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.