Each time the container is restarted, the schedules of the playlists are added to the existing cronjobs.
This leads to duplicated entries.
Also if a schedule is updated through the UI, this updated entry is added after a restart, leaving the original entry in the cronjob.
This results in the playlist schedule running on both the old as the new schedule.
Current workaround is manual editing the cronjob in the container after schedule change and container restart.
Explo version v1.1.3
Each time the container is restarted, the schedules of the playlists are added to the existing cronjobs.
This leads to duplicated entries.
Also if a schedule is updated through the UI, this updated entry is added after a restart, leaving the original entry in the cronjob.
This results in the playlist schedule running on both the old as the new schedule.
Current workaround is manual editing the cronjob in the container after schedule change and container restart.
Explo version v1.1.3