Symptom · one of six
Records go missing between systems
A sync error queue nobody watches. Below: what that means underneath, a check you can run yourself in about ten minutes, and what it costs to put right if the check confirms it.
Nothing on this page is sent anywhere. The check runs in your own org.
What it is
A sync error queue nobody watches
Lead-to-contact conversion drops records, prospects fail to reach Salesforce, and nothing alerts anyone because the errors land in a queue that has no owner. It is rarely one cause, and the first useful step is counting how many records are actually affected rather than arguing about why.
Confirm it yourself
How do you confirm this yourself?
In Account Engagement, open the sync error queue and read the oldest entry’s date. If it predates this quarter, nobody is watching it.
You have this if the oldest error in the queue predates this quarter. If your org comes back the other side of that line, this is not your problem, and nothing on this page is worth buying to you. Finding that out costs nothing and takes ten minutes.
If the check confirms it
Sync audit and repair, with monitoring that reports to a person
Fixed price on a written scope, 40 hours at fifty euro an hour, about 2 weeks elapsed. Documentation and sixty days of support after handover are in the price rather than an addition.
€2,000 · 40 hours · 2 weeks
When it is bigger than a repair
When is this the org rather than one fault?
This one travels with the numbers nobody believes, because figures built on a set with holes in it disagree with figures built on the source. If more than two of the six match at once, the pattern is usually one org that was never configured for how the company sells now, rather than several separate faults. That is an implementation, not a repair, and it is priced the same way: hours multiplied by fifty.
Asked often enough to answer here
Questions
The integration reports success. How can records be missing?
A green status means the call returned, not that the row arrived. Rejected records land in an error queue and the connector carries on. That is why the queue, not the status, is the thing to read.
Is this always a Pardot problem?
No. The same shape appears with any connector, and often the fault is a validation rule or a required field on the Salesforce side rejecting rows the sender considers valid.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 22 August 2026.