search

airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
https://airbyte.com
Other
15.69k stars 4.03k forks source link

[source-intercom] conversations/search failed with status code 404 and error message Conversation not found. Message deleted. #42853

Open proof-nicholas opened 2 months ago

proof-nicholas commented 2 months ago

Connector Name

Intercom

Connector Version

0.6.16

What step the error happened?

During the sync

Relevant information

We are getting the following error during all our Sync operations using this connector, causing it to partially fail:

"Sync Partially Succeeded: Request to https://api.intercom.io/conversations/search failed with status code 404 and error message Conversation not found. Message deleted."

My interpretation is that a conversation was deleted and Airbyte can't handle it not being there. Not sure why it would get stuck on this step though or how to get past it.

Any help would be appreciated, thanks!

Relevant log output

No response

Contribute

proof-nicholas commented 2 months ago

Hi, any update on this?

topefolorunso commented 1 month ago

I'm unable to reproduce this @proof-nicholas . Can you share your error logs?

proof-nicholas commented 1 month ago

How can I share with you the logs securely, thanks?

topefolorunso commented 1 month ago

How can I share with you the logs securely, thanks?

Ping me in slack (@topefolorunso)

topefolorunso commented 1 month ago

This issue was resolved in #36277. Apparently, something else is causing this.

Below is the cause of what was resolved in #36277

The issue is under the conversations stream, having the user that might be either an external customer, in this case, there is no opportunity to fetch the data for that conversation, that has been linked to the actual Intercom conversation because it's restricted for the External Users; or - it's a simply the user doesn't exist anymore and we are trying to fetch non-existent entity, which leads to the 404.

fix then was to downgrade from API v2.10 to v2.9. But since then, API has been upgraded to v2.11. Perhaps upgrading to v2.11 will fix this without breaking the previous fix. cc: @natikgadzhi