- Within an Active Sync - while a sync is actively running, if Hightouch receives any row-level errors it will automatically retry (at an exponential backoff) until a certain threshold of failure has been met. If a record continues to fail, Hightouch will formally consider it as
failed, which typically maxes out after a certain interval (specific to each destination). This is very similar to the process described by AWS in this documentation - Error retries and exponential backoff in AWS.
- On Subsequent Syncs - Hightouch will keep an index of all
failedrecords and will automatically retry them on every subsequent sync.
- During that single sync run, let's imagine 2 of those 5 records become available for update. Our automatic retries would retry and successfully update these 2 by process number 1 above.
- On the next subsequent run of the sync (at some custom interval in the future) we’d automatically try the remaining 3 records, described by process number 2 above.
- Connection issues with your data warehouse?
- Confusing API responses from destination systems?
- Unsupported destination objects or modes?
- Help with complex SQL queries?
Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.
If you see something that's missing from our app, let us know and we'll work with you to build it!
We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.