Scheduler — events that have to happen on time

A radio programme runs to a clock, not just a song order

A playlist answers the question “what comes next”, but radio also has to answer “what must happen at a specific time”. That is where the Scheduler comes in.

The Scheduler stores planned items and keeps track of their times. When a slot arrives, it decides whether the item should be started, whether it is still within the allowed time window, or whether it is too late and should be marked as missed. Items can be added, edited, temporarily disabled or removed.

Why delay tolerance matters

An event on the radio rarely happens in a vacuum. An ad break is due to start at 10:00, but at 09:59:58 a song is still playing. If the system reacts blindly to the second, it cuts content off at an unnatural moment. If there is no limit on lateness, an event planned for 10:00 could fire much later, when it no longer makes any sense.

That is why there is a maximum allowed delay setting: you decide how long an event remains valid after its scheduled time.

How it works in practice

Prepare the content or event in advance, set the time and let the system watch the clock. When the time comes, the Scheduler reacts according to the rules. If an event should not be started because it is too late, the system records it as missed — instead of dropping it into the wrong part of the programme.

A real-world example

A station ID or a special element needs to air in a specific part of the hour. Instead of the presenter watching the clock and looking for the file by hand, the event is prepared in advance and the Scheduler keeps track of the time while the playlist runs normally.

With a larger number of scheduled elements, the biggest benefit is not the automation itself but consistency: the same rules apply every day, regardless of whether someone remembered in time.