Hello team,
Anyone experienced this kind of issue before? Or any ideas what could be causing this on
tap-salesforce
?
r
Reuben (Matatika)
12/02/2025, 12:05 AM
Hard to say... Could be the API responding in an unexpected way, or perhaps the tap's incremental replication logic has a bug (maybe it assumes/expects data in ascending order by timestamp, and just takes the last value)?
Reuben (Matatika)
12/02/2025, 12:10 AM
I'd probably start by taking a look at where in the tap code the value is read from state and used in the following accounts/contacts request(s), and then how it figures out the "latest" value to update state with from the processed records.