The errors in this guide are specific to Pardot integrations. Refer to the Common SaaS extraction error reference for errors common to all SaaS integrations.

These errors will surface in the integration’s Extraction Logs.

Replication Key values are out of order

Detected out of order data. Current bookmark value [VALUE] is less than last bookmark value [VALUE]
Applicable to

Pardot v1 integrations

Level Critical

Replication Keys

Potential cause(s)

The most current Replication Key value returned by the Pardot API is less than the value Stitch has saved.

Some of the fields Stitch uses as Replication Keys are reported in Pardot using the preferred timezone of the user who authorized the integration in Stitch. For example: If the authorizing user has their preferred timezone set to EST, affected fields will contain time data reported in that timezone.

During Daylight Savings Time, the authorizing user’s preferred timezone can impact how time data is reported in Pardot and extracted by Stitch.

For example:

'2019-10-27 01:48:55',
'2019-10-27 01:54:08',
'2019-10-27 01:59:03',
'2019-10-27 01:00:17',  # Time reset back an hour for DST
'2019-10-27 01:03:53',
'2019-10-27 01:13:12'

To prevent data discrepancies from occurring, Stitch’s Pardot integration specifically checks for out of order data. When out of order data is detected, the Extraction will fail and result in this error in Stitch.

Suggested action(s)

Re-authorize the integration in Stitch with a Pardot user who has their preferred timezone set to UTC. If possible, consider creating a dedicated API user with a UTC timezone for use in Stitch.

Back to Pardot error list
Back to top

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.