Feature Disruption

We continue to roll out the fix across all impacted instances, and are monitoring progress until deployment is complete and services are fully stabilized.

We will provide an update once the rollout is complete, or sooner if new information becomes available.

There are no additional updates at this time. Our teams continue to assess streams created during the impact window and are actively working to restore those that were affected.
We will provide an update in 90 minutes or sooner if additional information becomes available.

We have deployed a fix to prevent new Data Cloud and Marketing Cloud CRM Connector Streams containing date-time and date-only field types from being affected by this issue. We continue to assess streams that were created during the impact window, and our teams are actively working to restore those affected streams.

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

After further investigation, we narrowed the scope of impacted instances and confirmed that some instances are no longer considered impacted. We will exclude those instances from future communications.
We apologize for any confusion this may have caused.

We believe we've identified the trigger of the issue impacting Data Cloud and Marketing Cloud streams. A recent code change incorrectly affects the handling of date-time and date-only fields, preventing new streams containing these field types from deploying successfully. We're developing a fix and it's currently in testing. Once validated, we will deploy this to all impacted instances. We also continue to assess the full scope of impact.

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

We're investigating a feature disruption issue impacting our Data Cloud and Marketing Cloud customers. When deploying a stream, some users are encountering an error and are unable to complete this action. We're trying to reproduce the issue as an initial resolution step to support ongoing troubleshooting. We are also reviewing any recent changes that may be contributing to the issue while also looking into the full scope of the impact.

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