-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Source Facebook: rate limit not always handled #3525
Comments
* fix backoff of batch requests * fix backoff of batch requests * fix tests * fix tests * fix requirements * fix tests * fix tests * sort codes * format * fix setup * fix integration tests * bump version * fix integration tests Co-authored-by: Eugene Kulak <[email protected]>
@keu @sherifnada This worked previously but today I'm getting this:
Did something change? It looks like the |
Also, when fetching adaccounts, error #80004 is getting triggered but it isn't getting caught. Haven't quite figured out why, yet — I've confirmed the correct version of the code is running.
|
Hi @zestyping,
|
Here's the full log with both errors. Note at the beginning it says it's running |
Let me know if you'd like me to export the Docker image of |
Interesting, I'm getting a new kind of error now: "did not start after 512 seconds". It's persistent after many retries. Here's the log:
|
Strangely, when I do the HTTP requests myself, everything runs fine and finishes in less than a minute. Here's my script fetching the daily ad metrics without any breakdowns:
With age and gender breakdowns:
With device and platform breakdowns:
|
@keu @sherifnada Here are the scripts I'm using above, so you can replicate what I'm seeing. I tried running the Airbyte sync again immediately after using these scripts, and the sync is still failing in the same way (which is evidence that it's not a transient issue that existed when Airbyte was running but not when my scripts were running). Airbyte must be doing something different, though I don't know what. Can we re-open this issue, or would you like to start a new one? |
@zestyping re-opening here since all context is already present in this ticket. Will get to work on this first thing on monday. |
Thanks @sherifnada! I hope the information here helps! |
@zestyping according to your logs both errors happened only when we read AdCreative stream, but your script reads only Insights data. Could you select only Insights streams and try sync with Airbyte? |
We definitely do things differently:
still looking into this issue... |
I tried again with
Full log attached. |
The scripts I included above also use the async API for insights. The |
I am trying again with only the Insights tables selected (I also removed |
Same failure as the first time, with only Insights. |
Hello. I am getting airbyte version : 0.27.4-alpha
Description : Here is the full log - |
Hi @mk556 , thanks for your report! I don't think your case is related to call rate, so may I ask you to create a separate issue for it? Also, AFAIK, we can't do much about solving timeout exceptions because this is a FB limitation, in general, it is not recommended to use Account level Insights. But we are actively working on one feature that should allow selecting only specific fields thus making request 'lighter' and less prone to timeouts: #2227 |
Description
A user reported the FB marketing source was not handling rate limiting gracefully and with no apparent sign of retry. Attached is the log:
logs-290-0.txt
Acceptance Criteria
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: