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

429 Error too many requests #22

Open
sammorrisdesign-zz opened this issue May 29, 2018 · 2 comments
Open

429 Error too many requests #22

sammorrisdesign-zz opened this issue May 29, 2018 · 2 comments

Comments

@sammorrisdesign-zz
Copy link

I've been having a little bit of an issue with this package. I've managed to figure out why it's happening. I think.

I'm trying to request too many worksheets at once (from what I can see). It might be worth throttling the number of requests made somehow. I've just put in a random delay to solve it for me but there's a probably a better way of doing it.

@bassarisse
Copy link
Owner

Sorry for the delay, and thank you for your time in reporting this.

I never experienced this error, but I'm not sure if it's something the package should (and could) handle.

Can you provide more details about your case, so we can investigate it further? Things like:

  • Auth method
  • Number of spreadsheets/worksheets you're fetching
  • Actual code (whether you're using CLI or Node API) or an example of it
  • How you implemented the mentioned "random delay"

@sammorrisdesign-zz
Copy link
Author

sammorrisdesign-zz commented Jul 1, 2018

I'm using a Google Service Account to authenticate. My Doc has 65 spreadsheets in it! Which I know is a lot and definitely not common, but it made sense for my project.

Here's the code. I actually ended up just passing in a list of sheets before any requests as the names are predictable in this case. I then fetched them one by one and waited for a response before continuing. It gets the job done, but it massively slows fetching down.

I'd understand if this is something you wouldn't want the package to support. It could easily be considered a weird edge case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants