# Pardot Extraction Error Reference

The errors in this guide are specific to Pardot integrations. Refer to the [Common SaaS extraction error reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/common-saas-extraction-error-reference) for errors common to all SaaS integrations.

These errors will surface in the integration’s [Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs).

* [Detected out of order data. Current bookmark value \[VALUE\] is less than last bookmark value \[VALUE\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/pardot-extraction-error-reference#out-of-order-data)

### Replication Key values are out of order

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

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

| **Applicable to** | Pardot v1 integrations |
| --- | --- |
| **Level** | Critical<br><br>the Remove icon<br><br>Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. |
| **Category** | Replication Keys |
| **Potential cause(s)** | The most current Replication Key value returned by the Pardot API is less than the value Stitch has saved.<br><br>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.<br><br>During Daylight Savings Time, the authorizing user’s preferred timezone can impact how time data is reported in Pardot and extracted by Stitch.<br><br>For example:<br><br>```<br>'2019-10-27 01:48:55',<br>'2019-10-27 01:54:08',<br>'2019-10-27 01:59:03',<br>'2019-10-27 01:00:17',  # Time reset back an hour for DST<br>'2019-10-27 01:03:53',<br>'2019-10-27 01:13:12'<br>```<br><br>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](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/pardot-extraction-error-reference#)  
[Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/pardot-extraction-error-reference#)