Column order not respected in subset of syncs

What to do

• Check whether you use Hightouch Destinations. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 40m it lasted.

  Anything that failed between 2025-10-23 16:01 UTC and 2025-10-23 20:41 UTC may need a replay.

• Subscribe to Hightouch's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=hightouch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Hightouch 3

1. investigatingOct 23, 2025, 4: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.

   provider

2. monitoringOct 23, 2025, 6: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.

   provider

3. resolvedOct 23, 2025, 8: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.