catch-up scheduling: filling the slot that already passed

Your channel is set to release at 8 AM every day. You shut down your computer and go about your day. At 8:05 nothing goes live. Under the old design, that slot was simply gone. Autoretto now looks at that missed slot differently. It is not a lost moment. It is a pending job that can still be done.

The scheduler changed how it picks an upload time. It does not wait for a future timestamp to arrive. Instead, it keys off the most recent past slot. That slot must be inside a catch-up window. The window is a short span of time that goes backward from now. It exists so the system does not try to fill a tiny gap from last week. The scheduler does this by comparing the current time to the slot times in your schedule. It finds the latest slot that is in the past and not yet marked as done. That is the slot that will be produced and uploaded next.

You might wonder why the window matters. Without it, the scheduler could look back forever. If you paused your channel for a month, it would try to upload weeks of missed slots all at once. That would spam your channel. So the window is tight. A slot that is too old simply falls away. The system focuses on recent gaps only. It is a balance between catching up and staying current. The exact length is set by the platform. You do not need to think about it.

The actual upload is driven by an hourly cron job. A cron job is a scheduled task that runs on a server. It checks for due slots without needing a browser to be open. This is a big change. It used to depend on a person keeping the app open. Now the check runs every hour, day or night. When the cron finds a due slot, it starts a chain. It pulls the latest generated audio and artwork. It renders a beat-synced video. It runs the quality and policy gates. It sends the video to YouTube. Because it uses the YouTube API directly, there is no need for a logged-in browser session. All of that happens in the background.

There is also a guard against duplicate work. It is called the last-release stamp. This is a tiny piece of data that records the slot that was just published. It is written right before the upload finishes. If two cron runs overlap, both might see the same due slot. The first run writes the stamp. The second run sees it and stops. This is important because rendering can take a few minutes. A second check could start a duplicate render. The stamp prevents that. It is a simple lock that keeps the pipeline safe.

Here is how it plays out. Your slot is 6 PM. The hourly cron runs at 5:00. It finds nothing. At 6:00 the cron runs again. The 6 PM slot is now the most recent past slot, and it is inside the window. The cron fires the render job. The render takes four minutes. At 7:00 the cron checks once more. The last-release stamp for 6 PM is already recorded. The scheduler does nothing. The video goes live at 6:04. It was not exactly on the dot, but it happened. You did not need to be there.

This design changes how you think about your schedule. A missed slot is not a lost slot. You do not need to keep a machine running. You do not need to keep a browser open. The system catches up on its own. The last-release stamp makes sure that catching up does not create messes. The scheduler is now a quiet worker in the background. It looks backward, fills holes, and stays out of your way.

All of this is part of a wider push to make publishing more reliable. The scheduler used to be a simple timer. Now it is a small queue manager. It knows what was supposed to happen and what actually happened. The gap between those two is where the work happens. Autoretto closes that gap without asking you to do anything.