Music that resumes after an interruption.
Keep playback coherent when schedules overlap.
Where this work fits
A song can still be playing when an advert or prayer is due. The player needs to know what takes priority, where to stop, and where to resume. Station changes and the venue’s local time add more boundaries to that same day.
I implemented ordering for music, adverts, and prayer interruptions. I preserved the amount of a track already played so it could resume afterward, and handled conflicts between interruptions rather than allowing them to compete for the same moment.
Interrupt, then resume in the right place
Watch the music lane split around the scheduled interruptions. The second music segment continues from the saved position rather than starting the song again.
Start on time without losing the song.
Giving an interruption priority solves only half the problem. I also had to preserve how much of the track had played, resolve conflicts between interruptions, and align what came next. Time-zone handling kept those decisions tied to the venue’s day.
The skills behind the work
- Queues & concurrency
- Control when work runs and how much runs at once, keeping expensive operations manageable.
- Time-zone handling
- Interpret schedules in the correct local time and handle boundaries consistently.
- State management
- Represent what is happening now and define which changes are valid next.
Scheduling errors fell, and interrupted tracks could continue from their saved position. Operators gained more control over when content played and how it fit into the rest of the schedule.
- Scheduling errors
- −80%After moving playlist and interruption logic from the frontend into backend services.