Open mjbartho opened 2 years ago
have you solved this, because i'm stuck at it and nothing works?
No, I didn't solve this. I was processing each of these videos in a managed workflow execution (AWS StepFunctions) and set up a wait step to wait an hour and then try again. I would try this loop for 1 week before failing the workflow. I would have preferred to trigger this wait step with an explicit signal (429 or a more accurate statusText), but I ended up casting the wide net and going into this wait cycle in response to 403 errors.
We are migrating our video catalog to a new processing and hosting solution and as a part of that, we need to transfer files that are currently housed in GoogleDrive. After around 60 videos transferred (our videos are typically between 100MB and 300MB), we start to see errors when trying to transfer the files which give a 403 error code with
statusText
"Forbidden".We are using the
drive.files.get
api to stream the file into S3I was retrying the file transfers to debug the issue, but the issue persisted. Once the hour turned 6:00 PM today, I happened to retry a few more and they succeeded.
This hints at some hourly egress limit. I was unable to find any documentation for this limit and this was not covered by the cases described in
https://developers.google.com/drive/api/guides/handle-errors
This is not strictly a request rate limiting issue so perhaps a 429 would not be appropriate, but a more explicit
statusText
would at least allow for more reasonable debugging.Environment details
googleapis
version: 39.2.0Steps to reproduce
Observe 403 error with message "Forbidden" like