SABnzbd Forums

I have a lot of pending downloads in SAB and all of them have a High priority set on them so pretty much the priority should be ignored. What I noticed is when I manually move one or two downloads up the queue they get downloaded if they're NOT yet finished after a few hours I look at the GUI again and noticed that they are not on the top of the list again. Any thoughts?

I cannot quote follow the story.
Please break up the sentences.

Basically what happens is this:

1.) I manually move one or two downloads on top of the queue.
2.) They are move successfully on top and the download continues.
3.) After a few hours, I check the queue and if they are still not yet finished I notice them NOT on top of the list again.

Is that clearer?

I think what's happening is that most of the items that I put on top of the queue have very many missing articles and then after quite some time they just go to the bottom of the list for some reason. Is this normal behavior? I have the "Abort jobs that cannot be completed" feature checked so I'm not sure why they're not being aborted. The missing articles already go up to 3000+ so isn't that obvious that the job will fail. Why does SAB still continue trying to download?

There's an option in Config->Switches to abort jobs that cannot be completed.

As stated above, I already have that checked? Sorry, I'm not sure where you're getting at?

It should abort the job when there is less repair articles available than articles missing. Weird that it continues 3000+ since we haven't seen that behavior before.

Could you maybe send us a screenshot of your whole queue and a download that looks like this to Safihre@sabnzbd.org?

Also this shouldn't change the order of the queue.

Ok, I'll try to send one but right now all I have is a download with 286 missing articles. But I reckon that that is already a lot. And I agree, this is the first time I had this behavior. It seems that it prioritizes the Making a Murderer series for some reason, it re-arranges the queue randomly.

Sent.

Found the problem in his kevindd992002's.
The switch 'Sort by Date' was turned on, causing the queue order to change every time Sonarr added a new NZB.