While sending a file to google drive we get the following error on all of our Zaps:
The app returned "Sorry... body { font-family: verdana, arial, sans-serif; background-color: #fff; color: #000; }GoogleSorry...We're sorry...... but your computer or network may be sending automated queries. To protect...". Sorry... body { font-family: verdana, arial, sans-serif; background-color: #fff; color: #000; }GoogleSorry...We're sorry...... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.See Google Help for more information.Google Home
How can we fix this? It’s not a field error of any kind.
Best regards, BridgeBV
Best answer
Google Drive getting 403 "We're sorry... but your computer or network may be sending automated queries" Error
- Beginner
- 3 replies
Best answer by DanversBest answer by Danvers
Hi everyone!
I’m happy to let you know that we’ve rolled out a fix for this issue. If you saw the “Run was throttled” error you should now be able to successfully replay your tasks.
We know that some users are still seeing some 502 errors but much less frequently. We’re keeping an eye on things to make sure that this doesn’t increase, so if you do run into this error again, please contact the Support Team using the Get Help form.
You can learn more about this issue and how it was resolved on this Zapier Status incident page.
Show first post
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
Please also notify me when this is fixed. Any workarounds for previously failed zaps as issue seems to be somewhat intermittent?
This issue is preventing a launch of a new internal dataflow we’ve been building all year! Would love an update ASAP!
+6- Zapier Staff
- 2435 replies
Hi Everyone,
I’ve added all of you to the list of affected users, and we’ll notify each one via email once an update is available. Thanks!
Don’t know if this will help anyone, or whether it is purely coincedence but we have two zaps that are calling the same app and both going to Google Drive on the REPLACE function. Set up identically, just a different source from the app and a different folder in Google Drive.
ZAP B lets call it, failed on the 7th but after that continued to work, so I looked into what was different in the set up. Zap B has the share “Anyone with a link” as an Editor enabled but Zap A didn’t. Yesterday (GMT) I set Zap A to be exactly the same and this morning it has run as expected, previously it had failed numerous days. I know there is a risk of making the sheet “”OPEN”” but if as a temporary measure it gets us out of this situation, its worth taking a risk until Zapier come up with a fix. I hope this might be a help for some, maybe not all but it has worked for us.
The fact this works with an “”OPEN”” sheet makes me think this is an authorisation issue on Google’s end.
I will keep monitoring these zaps but hopefully a fix is on the horizon.
- Beginner
- 3 replies
Same issue has started to occur for my company as well. Can I please be added to the update list?
Thanks.
+6- Zapier Staff
- 2435 replies
Hi everyone,
I recently added a few more members to the list of affected users, and we’ll notify everyone via email once an update is available. Thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.