A call that Navidrome kills now gets a next attempt.
Before, when the host killed a generation call ("context deadline exceeded"), nothing ran again until the next daily run. By then the plugin had forgotten the kill, so it asked for the same big bite and was killed again, every day.
Now each call schedules its own successor two minutes out before it starts, and removes it when it returns. After a kill, the next attempt comes two minutes later and asks for less. On a server where this happens, the Navidrome log now shows the previous call never returned (killed in ...). If even the smallest bite is killed, the plugin says giving up for now and waits for the next daily run, as before.
This was tested with unit tests against a model of Navidrome's scheduler, not yet on a live server.
Which file do I download?
- Navidrome 0.63.x:
navibeat-mixes.ndp. - Navidrome 0.64.0 or newer:
navibeat-mixes-navidrome-0.64.ndp.
Important on 0.64: rename the file. Navidrome knows a plugin by its file name, and it keeps the plugin's settings and learned listening history under that name. Rename navibeat-mixes-navidrome-0.64.ndp to navibeat-mixes.ndp and put it in place of the old file. Keep only one NaviBeat Mixes file in the plugins folder.
To update: download the file for your Navidrome version, replace the file in your plugins folder (rename it first on 0.64), restart Navidrome, and enable the plugin again in Settings > Plugins.