Feature Disruption

The Technology team has deployed the latest version of the release which contains the fix to resolve the Sandbox Refresh issue to all the affected instances and it is expected to take one hour. Teams will continue to perform validations and health checks.

We’ll provide an update in 2 hours or sooner if additional information becomes available.

The Release Management team has finished the deployment on test instances and it was successful. The Technology team is continuing to perform post-deployment validations. The next action is to deploy this latest version of the release to the affected instances. This will address the sandbox refresh and Experience Cloud builder issue. The deployment to the remaining affected instances is expected to take several hours.

We’ll provide an update in 2 hours or sooner if additional information becomes available.

The Technology team has decided to proceed with a fix forward as a path to resolution for the Experience Cloud builder issue. This will address the sandbox refresh issue. The team is currently testing the fix forward and validating whether it will be successful before releasing it to the impacted PODs. The testing and deployment to production is expected to take several hours.

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

Correction: Customers on instance AP18 may have been notified of this issue in error. This instance has been removed from future postings.

One of the test instances has shown positive results and resolved the experience builder issue. Engineers are moving ahead with a fix forward to update the remaining affected instances to the latest version. This will trigger a sandbox issue and the team is aware of this move forward. A fix for the Sandbox refresh issue is being prepared and will be deployed after testing.

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

The Release Management team is currently working on deploying the latest release version on two test instances one each from 1P core and Hyperforce.

Further impacted analysis and reviewing additional diagnostic logs we noted this to be a feature disruption. We apologize for any confusion this may have caused.

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

Correction: We initially communicated this issue to be a service disruption. However, after further impacted analysis and reviewing additional diagnostic logs we noted this to be a feature disruption. We apologize for any confusion this may have caused.

The Technology team has confirmed that rolling back to older versions of the release is not bringing the affected instances out of impact. The Release management team is working on deploying the latest version through an emergency release to the entire fleet of affected sandbox instances.

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

Experience Cloud sites are accessible, however, admins can’t access their community builders in the admin console. Rolling back two of the affected sandbox instances to an older version was tested, however, has not shown positive results. The Technology team has decided to move forward with the latest release version as a fix for the affected instances.

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

The Technology team determined that a rollback performed to mitigate a sandbox wide issue may have been a trigger for this incident. The team has also clarified the impact and currently customers are receiving an error message when trying to open the builder for sandboxes.

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

At 06:03 UTC, on July 5, 2023, the Salesforce Technology team became aware of a service disruption impacting Experience Cloud across multiple regions. This issue impacts sandboxes and isn’t impacting customers' production environments. The team is investigating the trigger for the issue and is attempting a rollback to a previous version to resolve the issue.


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