How Autoretto decides which slot to upload

People ask how the schedule actually works. The short answer is that Autoretto does not wait for a future time. It looks back. The scheduler scans your calendar of slots and picks the most recent one that is still inside a catch-up window. That is the slot that gets the video. This might feel odd, but it solves a real problem. A future timestamp is fragile. If the machine is off or the network is down, you lose that release. Looking back means no slot ever gets skipped.

The catch-up window is a fixed amount of time around each slot. If a slot is due at 2 PM, the window might extend for a few hours. At 3 PM, that slot is still the one the scheduler cares about. At 5 PM, it might fall out of the window. Then the next slot becomes the target. This keeps the publication close to the intended time without pretending the world is perfect. It also gives the pipeline time to render and check the video.

The scheduler runs on a loop, but it also has an hourly cron. The cron is a separate process. It does not need a browser to be open. It wakes up once an hour and drains any slots that are due. That means Autoretto can publish even if you are away from the computer. The visual editor is only for configuring your channel. The actual publishing logic lives in a service that runs independently. So you can set a schedule and close the laptop. The videos still go out.

There is a guard against double publishing. It is a simple last-release stamp. Every time a video is published, Autoretto writes a stamp with that release's ID and the slot it filled. Before any new upload, the system checks the stamp. If the slot already has a stamp, it moves on. This matters because loops and the cron can overlap. Two processes might both see the same due slot. The stamp ensures only one of them uploads. It is a small detail, but it prevents a messy channel.

Here is how it plays out in practice. You set a slot for 2 PM. Your computer is asleep at that exact minute. At 3:10 the machine wakes up. The scheduler loop runs. It sees the 2 PM slot as the most recent past slot inside the catch-up window. It publishes the video. At 3:30 the hourly cron fires. It sees the same slot already has a release. The stamp is there. It also sees the next slot is still in the future. So it does nothing. You end up with exactly one upload.

This design came from watching real schedules fail. The early version relied on being online at the right minute. That worked when everything went right. It broke often enough to need a change. The catch-up window and the cron make the system tolerant. The stamp makes it safe. The result is a schedule that behaves like an old radio station. It might be a few minutes late, but it always plays the show. Your audience sees a consistent release time and no duplicates.

You do not have to change how you use Autoretto. The scheduling page looks the same as before. You still pick slots and let the platform handle the rest. The difference is internal. The scheduler is now more honest about how computers work. It does not assume perfect uptime. It works with the mess of real machines. That is a quiet reliability win. It is the kind of fix that is invisible until you notice the missing upload never happens anymore.

The next time you see a video land a few minutes after the slot, you know why. It is not a delay. It is the system picking the most recent due slot and then checking the stamp. That is the actual connection between a schedule and an upload. It is a small piece of logic, but it removes a lot of guesswork.