Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users

Update timeline

1. identified Sep 03, 2026, 10:30 PM UTC

   Degradation Started: featurePerfDegradation

2. monitoring Sep 03, 2026, 10:40 PM UTC

   Data Cloud customers using batch transforms may see completed jobs remain in an outdated status in the user interface. Automated flows, subsequent transforms, or other downstream processes that depend on the status update may not initiate, potentially delaying downstream data processing. Transform jobs continue to complete successfully, and no impact to the processed data has been identified. We have identified the trigger and initiated a roll back which is expected to remediate the issue. We will provide an update upon completion of the roll back, or sooner if more information becomes available.

3. monitoring Sep 04, 2026, 12:20 AM UTC

   As we complete the rollback on individual instances, we will post instance-level updates to accurately reflect each instance’s impact end time. Once an instance has been rolled back, we will remove it from this main post. Instances where rollback is still in progress will continue to receive updates in this post until remediation is complete.

4. monitoring Sep 04, 2026, 01:35 AM UTC

   Due to a functional issue identified following the rollback, we’ve now paused this activity. We are creating a roll-forward fix to address both the original issue and the new functional impact. Users may now experience that their manual and scheduled transform runs fail to start. This was first identified at 20:10 UTC, September 3. We will provide the next update once we can clarify how long the fix-forward will take to verify and deploy, or when new information becomes available. We apologize for any inconvenience this is causing to customers.