Hi Wendy,
Thank you for your response. I’ve been able to reproduce it pretty often and the delays sometimes differ.
I edited 10 contacts’ state/region property in Hubspot by selecting 10 contacts then clicking edit from the main list/view all contacts page
I then made an API call to the get recently modified contactsAPI with query param count=10. On this request I get back 10 last modified contacts. Notice that the first one (the most recent) has a timestamp of 1593001672723
1st request response { "contacts": [ { "addedAt": 1593001672723, - Pastebin.com
The contact IDs are returned in the order of
2751
2851
2801
2901
3401
2651
2401
2451
1751
2551
I make the same request a few moments later and get back the following
Note that the first contact is still 2751 with the same timestamp as before - 1593001672723
2nd request response { "contacts": [ { "addedAt": 1593001672723, - Pastebin.com
However this time the order is
2751
2851
2801
2901
3051
3401
2651
2401
2451
1751
3501 was added retroactively.
The only way we know to solve for this essentially processes all contacts twice using this endpoint which uses a lot of our API requests and makes this process very inefficient. Our hope is that Hubspot can fix this issue so that contacts are not added to this list retroactively.
The maximum delay we’ve seen is 22 minutes but it is hard to say that the delay won’t ever be longer than that.
For more context we are trying to capture any contacts that are updated in the Hubspot system. The issue we have with webhooks is that we can’t support all of our customers custom fields. We also looked at using the new V3 Search API but also found the same delay issues with that API in addition to some other weird behaviors.
We greatly appreciate your help!