Hightouch incident

Column order not respected in subset of syncs

Resolved after 4 hours 40 minutes, affecting Destinations, on October 23, 2025.

resolved Oct 23, 2025, 08:41 PM UTC

Customer impact: - Syncs to S3 using All mode did not respect column order when writing data to the destination file. - Customers may have experienced failures for syncs to SFDC using Archive mode. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.

Started
Oct 23, 2025, 04:01 PM UTC
Resolved
Oct 23, 2025, 08:41 PM UTC
Duration
4h 40m
Detected by Pingoru
Oct 23, 2025, 04:01 PM UTC

Affected components

Destinations

Update timeline

  1. investigating Oct 23, 2025, 04:01 PM UTC

    We’re investigating an issue causing a subset of Hightouch file drop destinations to not respect column order when writing data to the destination file. File drop syncs to S3 and SFDC in Archive mode were impacted If you are seeing your data incorrectly ordered, rerunning your sync should resolve the issue.

  2. monitoring Oct 23, 2025, 06:27 PM UTC

    A fix has been implemented and we are monitoring the results. No action is required. The next scheduled sync will resolve the issue, or you can manually trigger one at any time.

  3. resolved Oct 23, 2025, 08:41 PM UTC

    Customer impact: - Syncs to S3 using All mode did not respect column order when writing data to the destination file. - Customers may have experienced failures for syncs to SFDC using Archive mode. No action is required. Syncs will resume on their next scheduled run, or you can manually trigger a run at any time.

Your product runs on more than Hightouch

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →