Data Cloud Feature Disruption

We have identified a fix and are rolling it out to the impacted instances. We expect it to be completed in approximately two hours.

We’ll provide an update upon completion of the fix or sooner if additional information becomes available.

We’ve identified a recent change that may have triggered this issue and are actively exploring multiple strategies to mitigate the impact and restore services as quickly as possible.

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

We are continuing to work with the third party to determine whether the limit increase has helped alleviate some of the impact. Alternatively, we are exploring multiple paths to resolution.

Additionally, investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact.

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

The limit is being increased by the third-party. In parallel, a recent change has been identified on the Salesforce side, which is being rolled back on a test instance to determine if this may have caused the impact.

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

Further investigation has highlighted that an API request limit is being reached on the third-party vendor side. A request to raise the limit is being pursued as a mitigation step.

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

We are investigating the feature disruption impacting Segmentation Publishing. Segmentation jobs are failing, and customers are observing errors in the Publish History.

We have determined that this may be related to an issue with a third-party service provider. We have contacted the provider and are actively troubleshooting with them.

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