-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Regularly Hit API limits on Zendesk Support #11899
Comments
Issue seems to be presented here but not resolved |
Please share the full log, and do not cancel the sync manually, we should see the exact place where the issue appears, from the partial logs you've shared in the description i cannot confirm that the "Tickets" stream was even synced. 429 error is the typical API error message when you hit the API RateLimits, as far as i can see it handled correctly, this message is just FYI, it should not cause the sync failure directly. |
@bazarnov take a look at the logs above, specifically the time difference between these rows
i have to cancel it, otherwise it just hangs and eventually my instance crashes. it hangs at various points but always at a
it varies how far it gets each time. sometimes I wait up to 6 hours before my instance crashes |
I have reverted to zendesk support
which this latest version does not show. Also the number of users is being capped at 100,000 in the latest version but does not appear the be the case with this earlier version (see other issue #11895) |
Please see attached full logs for a sync, there is no 429 error and the sync just hangs for 7 hours before I decide to cancel it specific lines
|
You've got a lot of data, please do not cancel the sync, let it fail, if it fails, and send the logs here, thank you. |
Is something happening in those 7 hours that I'm not aware of? In the previous comment I attached full logs although yes I cancelled it. Is there a reason I should let it hang beyond 7 hours? It ends up crashing our production airbyte instance. If there is a valid reason to let it run until failure (or airbyte instance crashes, which the logs are then still of not use) then please let me know. |
The reason I'm asking to let it run until it crashes is the actual crashed log, we should understand what is the main point of crashing, because due to the logs provided above, there is no sign that connector Zendesk Support fails at all. So my suggestion here is to decrease the The expected result: Zendesk Support connector doesn't crash and your instance either. |
Sorry to hijack this thread but wanted to confirm with you @danieldiamond that when you say:
Does this issue accurately describe what you're surfacing: #10829? We're actively working on improving this connector so thank you for helping us surface all these bugs and reporting them! |
hey @misteryeo thanks for reaching out. the issue on duplicate records was actually relating to "at-least-once" framework which is discussed further here. tldr; I am not using any normalization method and so incremental+dedupe is not available. and incremental will always pull the latest record again |
@bazarnov i left out this screenshot but essentially on older version |
@bazarnov just FYI there's still something going on with the main incremental stream. |
I'm having the same issue as you do, with ticket_metric stream failing and this error message : :"Rate limited by Zendesk edge protection". See logs attached. |
Hi,
What is very odd (and I don't understand) is that Airbyte reports the sync as Failed after the 3 tries. However, at the bottom of the logs it says:
And I see data loaded in BigQuery from the 1st of January 2020 (initial date in the source) to the 26th of September 2021. It contains around 102K rows. It seems to me as if the connector is trying to synchronise all the data from the start date every time, instead of picking up on the last synchronised date. I uploaded the log to Google drive for reference: https://drive.google.com/file/d/1u2dB6xx5Mqfyqsqn8MOlN1Au4n5L3xMh/view?usp=sharing Thanks. |
@lluisgassovillarejo |
Environment
Current Behavior
Regularly hitting the API limits for this connector. We have a few APIs hitting zendesk support but with this airbyte connector there is a massive surge on requests that cause rate limiting to apply. This in turn causes the airbyte instance to crash as it does not appear to handle the rate limiting appropriately.
This would be less of an issue if I were able to use the incremental stream. However, I am unable to use the incremental stream as it has its own issues i.e. returning duplicate records.
Expected Behavior
Syncs should be infrequent enough to prevent rate limiting. Alternatively, there should be an option for users to modify the rate limiting behaviour in the airbyte connector.
Logs
If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.
LOG
Steps to Reproduce
Are you willing to submit a PR?
No
The text was updated successfully, but these errors were encountered: