You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our build process uploads a 6GB tarball to GDrive. Recently and without any changes made, we started to receive this error:
Error: creating/updating file failed with error: googleapi: got HTTP response code 429 with body:
No body was output. The time between the previous log message ("No similar files found. Creating a new file") and the one above was ~7 minutes.
We're a paying GApps customer, so I doubt the size issue is the culprit. I also deleted some previous uploads in the same directory, made by the same API key -- an attempt to ensure that some sort of per-user, etc. limits are causing our problem. Didn't help, but I didn't expect it to either.
I presume the cause is either (1) some change to Google's throttling policies, or (2) an issue with how our account is set-up. I'm posting this to see if others have experienced this issue. No idea if there's a workaround that could be implemented in this action.
The text was updated successfully, but these errors were encountered:
Version used: main
Our build process uploads a 6GB tarball to GDrive. Recently and without any changes made, we started to receive this error:
Error: creating/updating file failed with error: googleapi: got HTTP response code 429 with body:
No body was output. The time between the previous log message ("No similar files found. Creating a new file") and the one above was ~7 minutes.
We're a paying GApps customer, so I doubt the size issue is the culprit. I also deleted some previous uploads in the same directory, made by the same API key -- an attempt to ensure that some sort of per-user, etc. limits are causing our problem. Didn't help, but I didn't expect it to either.
I presume the cause is either (1) some change to Google's throttling policies, or (2) an issue with how our account is set-up. I'm posting this to see if others have experienced this issue. No idea if there's a workaround that could be implemented in this action.
The text was updated successfully, but these errors were encountered: