Thanks for looping back around to update the thread, @blueguy! You beat us to it.

For anyone else following along, if you continue to receive errors, definitely reach out to support team and they can do a bit more digging for ya. 

I just got this from Zapier:

I’m reaching out because you may have received the following error from the Google Sheets integration: "Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute' of service 'sheets.googleapis.com' for consumer 'project_number:927538837578'." I wanted to let you know we recently got these quota limits increased for the Google Sheets integration which should resolve these error with no action needed from your end. If you continue to see this specific error, please don't hesitate to reach out. Have a great one!

Thank you Zapier!!

We too are experiencing the same issue. Any update?

Thank you for letting us know,@e.dgr. I’ve got you added to the list of affected users!

I definitely appreciate you sharing your candid feedback,@blueguy. While I can’t provide you with an ETA, I do want to reassure your thoughts aren’t falling on deaf ears. The team is actively digging into this and hopefully, we’ll have more news for you soon. 

For anyone who may be following along I also wanted to share some of what was discussed in the support ticket in case it adds any clarity:

...the error wasn't caused by the traffic in your Zap (specific to your user account) but rather an accumulation of requests coming from all user accounts from Zapier.

Unfortunately, this must be resolved at a platform level by our team responsible for the Google Sheets integration, as we may require an increase of rate-limits allowed.

Running into this issue as well - appreciate Zapier looking into a fix! Have many workflows running on Sheets. The chance of them working as intended has been sort of 50/50 since this issue started appearing ~a week ago

Please add me to the list of users affected by this, @christina.d. I’d appreciate any updates as they become available.

We are experiencing the same issues. And for us the issue is VERY serious. Errors have meant that we have failed to provide the service that the customers have paid for and it has really negatively impacted our business and customer satisfaction. :/

So please add me to the list of users affected by this, @christina.d.

Thanks for reaching out here @NoahFr, @JacobW, @jayarr and @martinsimmermann. Really sorry that you’re all running into these errors as well. I’ve gone ahead and added all of you the the list of affected users. We’ll be in touch as soon as it’s resolved.

Hi, we’re also experiencing this problem, so please add me to the list of affected users. We have lots of Zaps relying on Google Sheets, and this is becoming a concern.

Hi @SamB - we are now experiencing this issue as well.  Please add us to the list of affected users.

I agree with Martin above!! This is an issue.

Here are some more errors in the past 60 min alone!!

Thanks for letting us know @TheHistoryQuill and @Greg_GW. I’ve got you both added to the list of impacted users. We’ll be sure to let ya’ll know and keep the thread updated once there’s a fix in place!

Our team is also affected by these errors. Going to look at alternative integration solutions. Don’t believe these issues are happening with tray.io or automate.io. 

I’m really sorry to hear that, @BazookaJoe. I’ve gone ahead and added you to the list of affected users.

I don’t know whether tray.io/automate.io are running into similar issues but we’ll be sure to email you the minute this issue has been fixed.

@SamB Can you please add me to the list of impacted users as well? We have been experiencing the same issue detailed in this thread.

Here are some more errors messages that came in today:

Now I am posting these not to complain but try to help here.  Both of these errors occurred at the same time: it was on a Saturday morning at 9:52 AM.  However, our business was not even open during this time so it was “impossible” for these ZAPS to trigger in the first place. 

So I am wondering what is going on here?  Why am I getting errors on ZAPS that should not be triggering?

Thoughts?

gml 

Hi @Jack H. and @blueguy! 

@Jack H., it looks as though you’ve already been added to the list of impacted users by our Support team. We’ll be in touch as soon as we have any updates to share!

@blueguy, I’m not certain what trigger you’re using for those Zaps but if it’s using a polling rather than instant type of trigger then it’s possible for the Zap to be triggered (or at least attempt to trigger) outside of working hours.

With polling triggers the Zap will check the trigger app at regular intervals (every 1 to 15 minutes depending on your plan) to see if there’s been any updates and if there has it will trigger for them. And equally, if the Zap runs into an error while checking we’ll send you a notification about that, which appears to be the case here.

You can find out more about the difference between polling and instant triggers here: Trigger Types 

Hope that helps! 

We are also being affected.  Three different google sheet time out issues.  We have had several in between that have gone through.  So it is hit and miss.  Thanks for researching this.  We’ll check back here for updates.

Hi @ablit! You’ve been added to the list of impacted users. Thanks for hanging in there with us. We’ll let you know as soon as there’s a fix in place!

It has been 3 weeks and I am still getting the same error message.

Is there any new information to pass along?  Is this the best that customer service can do with a critical tool like this?  What happened to the priority related to this issue?

Can we not do better?

gml

Hey there @blueguy and @rpmats! 

I’m so sorry about these rate limit errors, that’s not want we want for you at all! Looking at the conversation @blueguy had with our Support team it appears that they’ve been added to a bug report for this issue. 

@rpmats, I’ve added you to the list of affected users on that bug report as well. I can’t make any promises as to when it will be fixed but we’ll be sure to email you both and post an update here once it is. In the meantime, using an alternative app should indeed help to get around these rate limit errors we’re seeing with Google Sheets!  

Troy: 

This is a zap that triggers about 40 times over an 8 hour period; it is a check in ZAP in a medical office.  So I cannot imagine that there are too many requests being made on the Google Sheet.

I will see how it performs with the delays…

I will keep you posted.

@blueguy 

Probably best to open a ticket with Zapier Support for them to troubleshoot further for you: https://zapier.com/app/get-help

I opened the ticket and this was the analysis:

Thank you for your follow-up, happy to clarify further.
 
I dug into the internal detailed logs of your example https://zapier.com/app/editor/146997153?context=10592680 Zap and retrieved the error logs coming from Google Sheets. I've attached it here: https://cdn.zapier.com/storage/files/95f13ec73123b6ca6a178c768c38faee_3.txt
 

 
The "per project" referenced here indicates that your Zaps are not encountering user account specific limits but rather platform wide limits on our Google Sheets integration. 
 
I dug into the internal logs for the recurrence of the 429 error code across all users (who have Zaps with Google Sheets) and the spikes approximately correspond to the times that they happened in your Zap. Meaning that the error wasn't caused by the traffic in your Zap (specific to your user account) but rather an accumulation of requests coming from all user accounts from Zapier.
 
Unfortunately, this must be resolved at a platform level by our team responsible for the Google Sheets integration, as we may require an increase of rate-limits allowed.
 
I'm so sorry that I don't have better news for you here! Please reach out if you have more questions, I'm happy to help out.

MY Comments: BASICALLY THIS SHOULD BE HAPPENING TO ANYONE WHO IS USING ZAPIER AND GOOGLE SHEETS; IT IS SOMETHING UNIQUE TO THEIR PLATFORM.  WHY HAVEN’T OTHERS EXPERIENCED THIS OR IF THEY HAVE, WHERE IS THE CONCERN?

I AM SOMEWHAT CONCERNED ABOUT THIS BECAUSE IT IS HAPPENING WITH DEGREE OF FREQUENCY 

IT HAS NOTHING TO DO WITH DELAYS THAT I PUT INTO MY ZAPS!

GML

I am experiencing the exact same issue, FWIW. Had someone working on it all last night and I’ve been on it for a couple of hours this morning. Have you gotten any update on the ticket?