Page 1 of 1
Force Download single item moves on to force next nzb
Posted: March 1st, 2018, 7:07 am
by Bane1979
Hi all,
I've searched the forums and found a few topics but none to resolve the issue.
I'm on Win10, using edge(sorry)
scenario:
If my entire queue is paused, and I select a single item to force download, it does so nicely. Although, once complete, it just moves onto force the next item in the queue and so on until the queue is cleared.
Note: The queue status and individual item status remain as "paused" but the progress bar continues to download.
Has anyone found a fix for this?
Re: Force Download single item moves on to force next nzb
Posted: March 1st, 2018, 1:25 pm
by safihre
So the thing is that the download-system will go and check if there's new articles beyond the Forced item to fill up any "empty" connections on your server, this is a bit of a known bug.
It shouldn't do the whole queue though..
To really only download the Force item, make sure you are on version 2.3.2 and then go to Config > Switches > Enable Advanced settings (top) > "Only Get Articles for Top of Queue"
Re: Force Download single item moves on to force next nzb
Posted: March 2nd, 2018, 1:21 am
by Bane1979
Thank you!
Makes sense. I'll enable the switch! (was so much simpler in older versions
)
Re: Force Download single item moves on to force next nzb
Posted: March 4th, 2018, 1:05 pm
by safihre
So it really continues through your whole queue? It doesn't stop at all after the Forced item is done?
Re: Force Download single item moves on to force next nzb
Posted: April 27th, 2018, 11:53 pm
by OneCD
Hello, I might jump in on this as I've just seen the same behavior.
Using SABnzbd 2.3.3 from the 'master' GitHub branch on Debian 9.4
Whole queue is paused. First item is changed to 'forced' priority. It is downloading as expected. It is 3 hours old and is downloading from my priority 0 server that has 1,000 days retention.
However, much further down the queue, a really old item (2,679 days old) is also downloading from one of my lower priority servers (priority 4) that has much longer retention (3,000 days). The old queue item priority is 'normal' and is currently queue list item 153 out of 195.
If I grab that first item (the 'forced' one), and move it down so it's no longer forced, I can watch the connections drop (via a second browser), and also see the connections drop for the old item. Make that first item 'forced' again, and the old item starts again too.
This does seem to agree with @safihre's comments in the second post.
