Hi @jammer.solijon can you add me to the bug report as well please?

Please add me to the list as I am facing the same issue, thank you. 

Thank you all for your work on this and getting this issue resolved.

Kind regards,

Paul Luckett

Hi @AbstraktUser 

I’ve added you to the list of affected users, and we’ll notify you once an update is available. Thanks!

@jammer.solijon  We are also affected by this issue. Please add us as an impacted user? 

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!

Please add me too - thanks.

Just in case you are not on the update list:

Google Drive: Errors on Upload File action causing some Zaps to turn off
Incident resolved
The 503 and 429 errors appear to be resolved at this point. Intermittent 502 errors are still present, but at much lower levels than before.
Time posted
Dec 14, 16:28 PST
Components affected
Degraded Performance    Apps

I’m sure we will all keep monitoring this issue.

Hi everyone,

let me know please when bug is fixed

Thanks 

Tobia

Please notify me as well.

Please add me too

@jammer.solijon Please add me to the list of affected users as well. Thank you so much!

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!

Can you add me also?

Please add me as well

Please add me to the list, too! We also have several Zaps that monitor Google Drive. 

Same issue has started to occur for my company as well. Can I please be added to the update list?

Thanks.

Please can I be added to the bug report?

Can we please be notified as well. Affecting us quite a bit.

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.

Same problem for me since yesterday. Replaying errored zaps works a few times, but it seems to have a time limit. Waiting a few minutes, then replaying the next one does the job, but it is very annoying.

Would you please add me to the list of affected users plese? Thanks

Keep me in the bug fixing report as well, thank you!

Getting the same issues for the last 3 days as well

Could you please add me to the notification list as well? Thank you.

We have experienced the same issue for the last 3 days. We have had the same zaps working for years! We have found out that replaying the Zap can make it run successfully, but this is not always on the first try (+ you consume more tasks). Our organization relies on many of these reports automated by Zapier so this has been a headache. 

Could anyone also add me to the list of affected users, please?