First of all, thanks for bringing the
generate command back and improving it — things feel normal and intuitive again, which is great.
The new
“start earlier” option also makes sense and I understand the reasoning behind it.
I’d like to suggest one possible improvement regarding where this option is configured.
At the moment, since
start earlier is defined globally in
Settings > Scheduler, it also affects manual actions. For example, if it’s set to 3 minutes and I click
Run now on an event, the event does not start immediately but waits those 3 minutes.
This can be problematic in real-world situations — for instance, if a playlist is empty or incorrect and I want to regenerate it immediately. In that case, pressing
Run now and having to wait several minutes is not ideal.
In practice, most playlists are generated almost instantly (especially hourly ones), while some special cases may indeed need several minutes. Because of that, it might be better if the
start earlier offset was configurable
per scheduler event (in the Scheduler Wizard), instead of being a global setting.
That would allow:
- critical or heavy playlists to start earlier,
- simple or test events to run immediately,
- and manual Run now actions to behave as expected.
At the very least, it would be helpful if
Run now was excluded from the
start earlier offset and always executed immediately.