Hey all, we are running on the <new declarative in...
# ask-community-for-troubleshooting
n
Hey all, we are running on the new declarative intercom connector (0.2.0) and with every sync we have a small number (~0,01%) of contacts that don’t show up in the destination. The total contact count in the sync logs is always lower than the total number of contacts on Intercom. Could someone help me make sense of the manifest.yaml and debug this? My current theory is that it is somehow linked to the pagination. We are running in a full refresh mode, and I see that the “contacts” declaration is under “stream_incremental_search”. • Why is it using the
contacts/search
endpoint instead of
contacts
? • Given that the results are sorted using the
updated_at
field, could it be that the pagination breaks because while fetching the records some of them will get updated and skip to the end of the list? • What is the purpose of the record filter condition? (
{{ record['updated_at'] >= ( stream_state.get('prior_state', {}).get('updated_at', 0) if stream_state else stream_slice.get('prior_state', {}).get('updated_at', 0) ) }}
)
🙏 1
k
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. However, I can provide you with some resources that might help you understand the Intercom source connector better: 1. [Intercom Source Connector Documentation](https://docs.airbyte.com/integrations/sources/intercom) 2. [Airbyte Protocol](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol) 3. [Source Sync Modes](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol#source-sync-modes) I hope these resources can help you find the answers you're looking for.
n