Partial Sync Failures for Profiles Sync
Sep 9, 14:23 UTCSep 9, 21:42 UTC
Duration
7h 19m
Impact
Informational
Root cause
Not disclosed
Segment, 90 days
10 incidents
Affected
Not listed by the vendor.
Final update
We have implemented measures to prevent unintended traits from appearing in profile syncs, and syncs are now running as expected. Our teams are developing a long-term solution and will share guidance with impacted customers on how to address any previously affected data.
Timeline
- Resolved · Sep 9, 21:42 UTC
We have implemented measures to prevent unintended traits from appearing in profile syncs, and syncs are now running as expected. Our teams are developing a long-term solution and will share guidance with impacted customers on how to address any previously affected data.
- Identified · Sep 9, 14:23 UTC
Between August 28, 2025, 11:21 AM PT and September 5, 2025, 5:04 AM PT, certain internal computed traits were unintentionally synced to the profile_traits_updates raw table for some specific scenarios. This resulted in partial sync failures for that table because of a breach of the warehouse column limit, which prevented data from being fully written. To mitigate the issue, we have disabled the syncing of such traits going forward and are actively evaluating next steps to remediate the data that was already synced.
More from Segment
Full historyIntermittent failures scheduling warehouse jobs and processing Profile Syncslasted 2h 15mDelays to Realtime Audiences and Journeyslasted 2h 8mSegment event delivery issueslasted 16h 20mAudience & Journey data delivery delay in EU regionlasted 1h 16mBraze Web Event Delivery is experience event delivery issuelasted 8h 33mActions S3 is currently experience formatting issues with the delivered eventslasted 2h 10m