starkebn wrote: ↑16 Sep 2017, 13:04
thanks for looking into it, I guess a fix might be a long way off if you have to rewrite the entire script. If it happens again it shouldn't be too much of a problem, I fixed it the first time by disabling the script for that download.
Its most likely only a message printing issue, so the articles werent there. But to be 100% sure I need Verbose logs if you spot it again. To avoid the issue, you could up the AgeLimit option to say 6 hours.
starkebn wrote: ↑19 Sep 2017, 11:59
Is it possible that, if there's nothing in the download queue, then Completion doesn't run? I guess it's not really important but there can be 100s of Completion messages in the history when there is nothing in the queue.
It would be cool to be able to do that, but the script only prints messages with "Completion: ....". The messages you are referring too are printed by NZBGet, when it starts the script based on the scheduler settings. After this start I can only determine what is printed.
These scheduler settings are hardcoded in the script for each 15 min (version NZBGet 18+). A double-ling of the interval each time the queue is emtpy would be cool, but I guess then I have to make my script to change its code itself each time the script has run, and that ain't easy or possible I guess. Probably antivirus or so would kick in to when a script changes itself?
it seems it is possible code wise:
https://stackoverflow.com/questions/396 ... nge-itself. This would also require that NZBget reads the script prior to each check, so it updates the check interval each time the script runs, but I don't know if thats the case. I will look into it, but cant guarantee anything.