Commerce Cloud Service Disruption - Storefronts and Business Manager

In order to ensure a successful remediation, customers should not perform any merchant activities, including replication and job restarts, until we have confirmed on Trust that the POD is out of impact. Once we have declared that we are out of impact, customers will need to restart all jobs. We expect this to be in approximately 90 minutes (00:00 UTC).

We’ll provide the next update as soon as the POD is out of impact.

The remediation is progressing without issue and is expected to be completed within 2 to 3 hours.

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

Remediation is progressing, with completion estimated to be between 3 and 5 hours. In the meantime, customers may continue to encounter errors accessing Storefronts and Business Manager. Alternative mitigation strategies are being evaluated to expedite resolution.

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

Upon further investigation, we have determined that the current remediation strategy could take up to five hours to complete. During this time, customers will continue to see errors when accessing Storefronts and Business Manager. We will continue to assess possible alternative strategies to resolve this issue as quickly as possible.

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

Our teams have identified the trigger and determined that remediating it is expected to take approximately three hours. During this time, customers will continue to see errors when loading Storefronts.

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

At 16:15 UTC on October 30, 2024, the Salesforce Technology team noted a service disruption impacting Commerce Cloud customers on POD190. Customers are unable to access the Storefronts. Initial investigations indicate the disruption may be caused by a recent change. Our team is currently investigating the trigger and working to resolve the issue.

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