Do n8n.cloud users share Google Sheets quota?

Questions
1

It’s my first question on the forum. If I seem stupid, my apology.

I use n8n.cloud. I notice lately my workflow with Google Sheets node more and more often ran into the error “The service is receiving too many requests from you” as below. Even for one single execution within 10 minute. It never happened before until recently. The project number mentioned 498586711441 here is not created by me, and my own project in Google Cloud console showed no usage at all. I guess somehow n8n.cloud users share the 1k/minute quota. Am I right?

What is the error message (if any)?

{ "error": { "code": 429, "message": "Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute' of service 'sheets.googleapis.com' for consumer 'project_number:498586711441'.", "status": "RESOURCE_EXHAUSTED", "details": [ { "@type": "type.googleapis.com/google.rpc.ErrorInfo", "reason": "RATE_LIMIT_EXCEEDED", "domain": "googleapis.com", "metadata": { "service": "sheets.googleapis.com", "quota_metric": "sheets.googleapis.com/read_requests", "quota_location": "global", "quota_limit_value": "1000", "consumer": "projects/498586711441", "quota_limit": "ReadRequestsPerMinutePerProject" } }, { "@type": "type.googleapis.com/google.rpc.Help", "links": [ { "description": "Request a higher quota limit.", "url": "https://cloud.google.com/docs/quotas/help/request_increase" } ] } ] } }

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.76.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system:
2

Hi @xzmr

Not stupid at all! We noticed this issue and are already working on a fix.

It should get back to normal soon.

2 Likes
3

Hi thanks for the update! Looking forward to the fix.
Perhaps allowing n8n.cloud users use their own API credentials (via Google Cloud Console) is a not-bad idea, so that everyone uses their own quota.

4

hi all! this should now be resolved :slight_smile: let us know if not

5

After 1 week testing, “Quota exceeded for quota metric” doesn’t happen that often. It was almost every run, now it’s once in a while.

1 Like
8

I have the same issue. There are no loops in my workflow, and only a couple of simple Google Sheets nodes with max 2 filters. No idea why it’s exceeding the quota. No way I’m requesting over 100 requests a minute (or 8k which should be the limit)

image
image1712×705 131 KB

9

Same issue here, happened more and more frequently.

image
image606×336 11.3 KB

10

Same issue here :melting_face: .

Does anyone have a workaround to avoid this quota exceeded error?

Cheers!

2 Likes
11

Hey Team, will there be any fix for this issue?

2 Likes
12

Yes. Since June the issue has occurred more often than before.

2 Likes
13

facing this issue, google quota. please look into this at the earliest. workflow is getting disturbed due to this.

14

Hi @gualter , I think this issue is re-emerging. can you please look into it

16

You can try http node and call with google sheet api.
When creating credential, use google oauth 2 credential that can link to a client id and client secret instead of using google sheet oauth2 credential, which only asking you to login to assign credential.

Then when you calling the api, the quota usage will be shown on your google cloud dashboard. and it does not exceed the quota and the error does not happen on my side for now.

I think they definitely mix up the quota usage for different executions, even for different users, cuz this error also happens when you only do very few rows’ modification.

17

@Samyyy did this work for you with http?

18

This only works with Http, cuz sheet node only supports Google Sheet Oauth2 credential while Http node supports Google Oauth2 credential which is more general and you can link it with a client id.

This issue doesn’t appear until now, only thing is you need to replace all of the sheet nodes with http node.