Skip to main content
Best answer

Google Forms Error Quota Exceeded "Expensive Reads"


Did this topic help you find an answer to your question?
Show first post

102 replies

SM59
  • New
  • 1 reply
  • May 29, 2023

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.

 


GCY
  • 1 reply
  • May 29, 2023

I also started receiving the error yesterda, on May 28.


Jules Van

same issue for me - seems similar to an issue Zapier got last year and their own Google API quotas 


johnpienaar

We’re experiencing the same with our account as well. Please could you assist?


MeditSol
  • New
  • 1 reply
  • May 29, 2023

Same issue here. Please add us to the list of affected accounts too.


ctrs
  • New
  • 1 reply
  • May 29, 2023

Add me to the update list as well, please! Thanks!


0to9
  • New
  • 1 reply
  • May 29, 2023

Add us to the update list as well, we have a client with the same issues since 27 may and it’s missing out subscriptions to events.


bigchokeslam

I’m receiving this error as well:

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'.


rometime
  • New
  • 1 reply
  • May 30, 2023

Same issue since May 27th. Please include me into the update list. Thanks!

 


  • New
  • 2 replies
  • May 30, 2023

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'.

 

Please add me to the update list


D-andyou
  • New
  • 1 reply
  • May 30, 2023

Hello,

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'.


Hello,

 

We also have this same issue on our side :

 

 

Please, add us to the list as well.

 

Best.


tibor.martini

We have the same problem with one of our Zaps since last week


Oase Creative

@christina.d Also have this issue since this morning.. :(


mistyr35t

We’re receiving the same error - please add us to the impacted user list as well.


CSUMB Admissions Processing

Same error rec’d May 28, 2023, 1:01 PM.  Please add us to the impacted user list.


wanderingwoods

I’m receiving the same error, twice a day for each form starting May 26. Please add me to the impacted user list.


Chris at Food Forward

Please add me to the list of impacted users


SegunRealtor

Hello, I’ve been getting the same message and I cant figure out how to fix it. 


Steve Chon

@christina.d - please add us to the list of affected users as well. Thank you.


EliteAssistanceLLC
christina.d wrote:

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!

 @christina.d @SamB @chanelle @ken.a 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7890 replies
  • June 1, 2023

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:

  1. Copy the current Zap that’s affected
  2. In the Copy - use the Google Sheets New Spreadsheet Row (Team Drive) trigger.
  3. 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! 🤞


GCCFJ
  • New
  • 1 reply
  • June 2, 2023

Please could you add me to the list of affected users.


MR_Concept
Forum|alt.badge.img
  • Beginner
  • 11 replies
  • June 2, 2023

as for me I have not change anything and it seems ok for 4 days now 


Please add me to the list of affected users.  


Reply