ADD sync times for each channel

[allanlaal]

each channel should have their own sync times

use case A:

user has lots of playlists and lots of channels in each playlist. sync is unable to complete in the 6 mins alloted by Google

use case B:

user adds a new channel and wants all the videos from it from date X in the past

[Fabian42]

You should be able to just make two copies of the document.

On 9 Jan 2018 07:45, "Allan Laal" [email protected] wrote:

each channel should have their own sync times use case A:

user has lots of playlists and lots of channels in each playlist. sync is unable to complete in the 6 mins alloted by Google use case B:

user adds a new channel and wants all the videos from it from date X in the past

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Elijas/auto-youtube-subscription-playlist-2/issues/21, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ_vYtVi77XFmzlBqeBzuGIPOjhYKrLIks5tIwsOgaJpZM4RXYZb .

[allanlaal]

then I would have 26 documents to manage :(

[victorjzsun]

The only way to break execution up across different times is by adding more triggers or clicking run multiple times. Assuming there is some kind of action that starts the script, we can conditionally update two ways:

1. Given the set of rows that need to be updated, update only those rows' playlists
   • Start and end rows for each run time? Group rows (with some format) and next group to update
2. Given all the sync times of each channel, and the current time, update all matching channels

[JesperDramsch]

@allanlaal the newest version implements sync times per channel

[victorjzsun]

Closing this due to inactivity and mostly being resolved.

Use case A is either solved by using frequency per row or multiple documents if still hitting quota. Frequency per channel is probably too granular and doesn't provide much benefit over per row.

Use case B is also solved since frequency per row should gate all other rows from updating so only the new row should be targeted. If we still cannot update in one run, probably cause too many videos to add, therefore quota error hit rather than timeout error which we can't really fix.