December 10, 2025
Avoid Playlist Conflicts: Scheduling Back-to-Back Special Playlists
In preparation for the madness of March, here are some important reminders for scheduling back-to-back Special Playlists.
- The first Special Playlist MUST end before starting the second one. It is not possible to nest a Special Playlist inside a Special Playlist.
- It is possible to schedule back-to-back Special Playlists, but it MUST be done sequentially. It cannot be done as a background event.
- Sequentially, you would schedule all the Special Playlists in the sequential log back-to-back, with a hard sync on the first event. For example, SPL1 Hard time at 13:00, SPL2 next in line at 13:01, and SPL3 next at 13:02. No sync points needed for the second and 3rd event, they just need to be next in the log.
- From the above example, the End Special Playlist workflow for SPL1 and SPL2 MUST tell the system to go back to the last played event. This will allow the system to fire off the next Special Playlist that was in the log.
- For SPL3, the End Special Playlist command would tell the system to go to the current time of day.
- While each of the Special Playlists are in the log for 13:00, when creating the instance for each of the Special Playlists, it is possible to schedule spots from the actual time the game is expected to run. For example, SPL1: Pull spots from 13:00 – 15:00; SPL2: Pull spots from 15:01–16:00; and SPL 3: Pull spots from 16:01-19:00. Just make sure that Traffic schedules all the spots for each game within the window of time designated for that game.
