-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch and restore vids on quota error #62
Comments
These come back as error in the debugger and should therefore not update the timestamp, which means we add them on the next execution. |
Should also handle videos that can't be found (private) as described in #92 |
Yes, but that could mean adding the first few over and over again. It would be better if the script noticed the error, stopped the process and updated the timestamp to just after the last video that was added, so that it does not produce a thousand error messages, but only one, and can resume without user input the next time. This would also make the currently somewhat hardcoded limit of 200 videos unnecessary in many situations (but it could be nice to keep for other usecases). |
That is possible at least for getting videos for a channel. With an extra API call, we can retrieve the publish timestamp for each video and as you said, add videos in chronological order. This would require an extra quota usage of 200, aka 4 videos worth, but could be combined with other video-related filters (excluding shorts) that require the API call. |
I think I've finished implementing this feature here !127, but I would still like to do more testing since I can only really test quota exceeded stuff once a day ;( |
My implementation "stores" vids failed due to quota by dynamically updating last updated timestamp and making sure we always add videos to playlist oldest first. |
Catch vids not added to playlist on error and store somewhere.
Then add vids first on next run
The text was updated successfully, but these errors were encountered: