New user here. Im trying to create a Zap where when someone fills out a Google Form, it creates a task for me on Google Tasks. But I get this error message: Quota exceeded for quota metric 'Expensive Reads' and limit 'Expensive Reads per minute' of service 'forms.googleapis.com' for consumer 'project_number:927538837578'.
Any idea on how I can solve this or even what this means?
Best answer by SamBBest answer by SamB
I have good news, friends! 👋
The bug report relating to these “Quota Exceeded” errors has recently been closed. The Google Forms API quota limits have been increased which should help to prevent these errors from occurring again in the near future.
If however you find that you’re still running into these error please do let us know in the Community. Or alternatively reach out to our helpful Support team who will be happy to investigate further.
Hi I also received this error for all of my Google Form zaps this weekend, so can you add me to the list of impacted users? It looks like every Zap is still running properly, which is a relief.
Trigger partner failure: Quota exceeded for quota metric 'Expensive Reads' and limit 'Expensive Reads per minute' of service 'forms.googleapis.com' for consumer 'project_number:927538837578'.
Google Forms Trigger partner failure: Quota exceeded for quota metric 'Expensive Reads' and limit 'Expensive Reads per minute' of service 'forms.googleapis.com' for consumer 'project_number:927538837578'.
I am also experiencing this issue. I received an email with the same error on May 27th, May 28th and May 29th for both Zaps I have that are using google form.
Trigger partner failure: Quota exceeded for quota metric 'Expensive Reads' and limit 'Expensive Reads per minute' of service 'forms.googleapis.com' for consumer 'project_number:927538837578'.
Hey friends! Went back and did some digging and it looks like a bug was recently opened for this error. I’ve added you both as impacted users and we’ll email you once a fix is in place. We’ll also be sure to keep the thread updated as well.
Thanks for flagging this in community!
Would you be able to add my email into the effected user please? I am now having this same issue, word for word on zaps that have been working fine for awhile and others that were created recently!
Hi @Thomas Vermeule, @tibor.martini, @Oase Creative, @mistyr35t, @CSUMB Admissions Processing, @wanderingwoods, @Chris at Food Forward, @SegunRealtor, @Steve Chon and @EliteAssistanceLLC!
Really sorry about the delay in our response here. Happy to confirm that you’re all added to the list of affected users.
In the meantime, there’s been a workaround suggested by Support that has had success for some folks which you may want to try:
Essentially the workaround is to switch to a different type of trigger. The Google Forms New Form Submission is a Hybrid Trigger and Google Sheets New Spreadsheet Row (non Team-Drive) is a Hybrid Trigger. But the Google Sheets New Spreadsheet Row(Team Drive) is a Polling Trigger so that’s what you’ll want to try instead by following the workaround outlined below.
Potential workaround:
Copy the current Zap that’s affected
In the Copy - use the Google Sheets New Spreadsheet Row(Team Drive) trigger.
Turn the Copied Zap ON and the original Zap OFF.
That will leave you with 2 Zaps each using different Trigger types. The New Zap will use a Google Sheets Polling Trigger. The Original Zap will use the Google Forms Hybrid Trigger.
You would only want one Zap on at a time. For now, leave the Google Sheets Team Drive trigger Zap ON.
When we notify you that the issue with the Google Forms Trigger has been resolved - then you could turn the original Zap back ON if you prefer.”
Hopefully that workaround will help in the meantime! 🤞