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
Pardot v1 integrations
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
During Daylight Savings Time, the authorizing user’s preferred timezone can impact how time data is reported in Pardot and extracted by Stitch.
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.
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.