Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zendesk Support connector - Missing data #10613

Closed
Tracked by #11021
alexchouraki opened this issue Feb 24, 2022 · 2 comments · Fixed by #11349
Closed
Tracked by #11021

Zendesk Support connector - Missing data #10613

alexchouraki opened this issue Feb 24, 2022 · 2 comments · Fixed by #11349

Comments

@alexchouraki
Copy link
Contributor

Is this your first time deploying Airbyte: No
OS Version / Instance: Ubuntu 20.04 on AWS EC2
Deployment: Docker
Airbyte Version: 0.35.31-alpha
Source name: Zendesk Support (0.1.12)
Destination: Snowflake (0.4.15)

Hello,
It appears that some data is missing from the Zendesk Support integration - I can find some tickets in the UI that are not in my tables (which is easy to check for anyone using the connection because it means there are “gaps” in ids instead of having everything completely sequential.).

This is related to this : https://support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket-archiving
Basically, after 120 days since resolution, tickets are archived, and don’t show up in certain streams with the API.

This has several implications :

  • Discrepancies between Airbyte data and Zendesk’s internal reporting system
  • On incremental syncs, any full reset and re-sync will result in data loss (because some tickets that have been written incrementally will have been archived by then)

It’s not a big deal for me, but I think it might be problematic for some people using the connector. There are other API endpoints that contain the correct info - maybe it’s just a matter of using those ?

@bazarnov
Copy link
Collaborator

bazarnov commented Mar 23, 2022

I found out that the current implementation of the Tickets doesn't return archived/deleted records, it simply skips them, as mentioned in the documentation. We would need to move to the incremental/tickets.json endpoint to return all records.
Thanks for the issue, we will fix this as soon as possible.

@bazarnov bazarnov self-assigned this Mar 23, 2022
@bazarnov bazarnov moved this to In review (internal) in GL Roadmap Mar 23, 2022
@bazarnov bazarnov moved this from In review (internal) to In review (Airbyte) in GL Roadmap Mar 24, 2022
@bazarnov bazarnov moved this from In review (Airbyte) to Done in GL Roadmap Mar 27, 2022
@alexchouraki
Copy link
Contributor Author

Wonderful, thank you! Eager to try it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
5 participants