The S4M Daily Scheduler is a custom app which provides an interface to configure, test and automate the scheduling of the S4M assets. The daily list of S4M assets are pulled from a custom S4M data source and then scheduled evenly across the 24 hour period. This app provides a UI to the console app that originally served this purpose.
| Table of Contents | ||||
|---|---|---|---|---|
|
Create a new Channel Instance
...
| Tip |
|---|
Be sure to SAVE your changes using the File or Instance menus. |
Field | Example Value | Description |
|---|---|---|
Instance Name | BC1 | A name for this instance - typically the same as the station ID |
First Hour | 5 | The first hour of the day to start scheduling the assets into. 5 represents 5:00 am |
Occurrences | 40 | Repeats each item this many times in the 24 hour period |
Content Group | BC | The content group of the channel used |
Channel | Global News BC1 | The channel used for scheduling |
Media Content Group | BC | The content group of the Media bin |
Media Bin | BC1 Zone Ads | The Media bin where the assets associated media will be looked for
|
Project Content Group | Global | The content group to find the Project in |
Project Name | L-Frame 2022 Ad Zones | The project that contains the published asset scenes that will be used by the S4M assets. Must have scenes named:
(Required when creating a new asset because the scene names are defined as |
Media Field | media.media | The name of the media tag that the media will be assigned to |
...
Run
Last but not least is the Run tab where you can configure when the instance will be run or run it manually.
...
The app will only check for and run the scheduler if it is enabled via the toggle switch at the bottom of the app.
Enabled toggle switch |  |
Disabled toggle switch |  |
| Tip |
|---|
Note that only saved and enabled instances will be run automatically. |
...
Then it will check the next instance and see that its Run At time has not yet arrived. It will continue to wait, checking each minute to see if there are any new instances that are now ready to be run.
Log Output
There are 2 types of log data that are generated as of version 1.0.2. They are subject to being deleted automatically to avoid creating an overwhelming amount of log history unnecessarily.
Log Files
These files that use a .log extension include logging statements generated by the app in the process of its operations including errors that occur.
CSV Files
Each time the app generates a schedule for a station - it will generate a basic CSV file that shows the times and what S4M item was scheduled. It is named with the station name and the date.
Example:
BC 1 Test_2023321.csv
| Code Block | ||
|---|---|---|
| ||
StartTime,Title
2023-03-21 09:00:00,01015722
2023-03-21 09:02:08,01005157
2023-03-21 09:04:16,01014394
... |
If you open it in Excel you may only see the data and time up to the minute by default. To show the seconds detail you can change the formatting of the column from type General to type Time (or another custom format).
Troubleshooting
Missing Media Problem
We had a problem where some assets weren’t having their media attached automatically when the scheduler was running:
… every once in a while, an asset once ingested via the Media Folder Watcher fails to be attached to the schedule when the S4M Daily Scheduler runs.
The Media was in the system via the watchfolder on 12-02-2024 as expected and it was ingested into the DB into the BC1 Zone Ad Directory and on 12-04-2024 it was picked up by the S4M Daily Reader and scheduled.
Everything played out the way it’s supposed to….except this link. We had to manually link the asset to the media in the schedule.
(NOTE that the media are attached via a dynamic field.)
Solution
It's a configuration issue: (Dec 9, 2024)
The Media Folder Watcher was pushing media into the BC1 Zone Ads bin in the BC content group.
Meanwhile the S4M Scheduler is looking for them in L-Frame 2022 in Global content group.