Google sheet resources exhausted?

How To
1

I have had 11 rows in that Google sheet and almost used up all my credits for the month?
I have two scenarios running reading Google sheet every minute… now two minutes with less than 20 rows total. My scenarios got sut off… and now this.

I got a RateLimitError

[429] Resource has been exhausted (e.g. check quota).

Origin

Google Sheets

I don’t get it.

3

Hello @LauraParis and welcome to the Make Community!

RateLimitError means your scenario is reading or writing Google Sheets too quickly.
Here’s a little bit more on the subject specific to Google: इस्तेमाल करने की सीमा  |  Google Sheets  |  Google for Developers

With Google Sheets app, some modules run multiple API calls under the hood.
What is going wrong depends on how your scenario is structured.

Here’s more about it specific to Make: https://www.make.com/en/help/errors/how-to-handle-errors-in-make/429-errors

If you’re able to share more about your scenario without divulging any personal or other sensitive information, we can try to help you figure out what’s going on.

4

Thank you for your reply.

My scenario is reading new rows every two minutes and then sending them to a Zerobounce module.
I got “* `500: INTERNAL - Internal error encountered” several times now as well.

This is what I have done.

  • I have turned sequential processing to yes
  • In the Google sheet module - I have turned the maximum number of results to be worked with during one execution cycle to 1
  • added an error handling with a sleep module set at 62 seconds followed by a resume handling

I’m not very proficient in Make. Below is a link to a video of what I have done:

5

Thanks for the video explanation!

Doesn’t seem like anything there would cause your Rate Limit error, do you have other scenarios using Google Sheets? Please note that the limit applies to your account, any and all automations using your account contribute to the limit.

The way it is configured now it seems like it runs every 2 minutes and only takes max 1 new row at a time. So if you have 10 new rows, it will essentially take 20 minutes to process all of them, so definitely nothing that will cause rate limit errors. As for the 5xx errors, maybe Google is just acting up, I’ve seen a bit of that lately here in the Community.

As for the error handler Resume module, you shouldn’t need to use an error route on a Trigger module because the scenario would just re-run later if it was not successful.

I don’t imagine you have a recording of when it hits a rate limit error?