SABnzbd Forums

Windows 10_32
Glitter Night

I found out that I have the same issue with both 2.0.0 RC1 and 2.0.0 RC2. NZBs that are older than what my provider supports appear not to be detected as unavailable. Download just stops without any error. It continues with the next NZB when I pause the old NZB. I have configured to only download the NZB that is on the top of the download queue.

I use Hitnews as my Usenet provider and they keep files for 1600 days.

Have you set this limitation in the Config>Servers page for the server?

Yes indeed. If the NZB is older than the setting in config-servers-retention time, then downloading stops without any error message. But if I change the retention time setting in config-servers-retention time to a value higher than the age of the NZB, or to zero, then downloading starts as normal.

I tried to reproduce this, but so far I could not.

How many servers do you have active? Only the 1, right?
Do you have 'Abort jobs that cannot be completed' turned on?

What I see happening is that (very slowly) it will try each article and realize it's too old, this is slow, but eventually it will discard the download.

Check before download is off
Only Get Articles for Top of Queue is on
Pre-queue user script is none
Abort jobs that cannot be completed is on

I have two servers configured. Both not optional. One with priority 0 and the other one with priority 1. The priority 0 server has a retention time of 1600 and the other 10. Only the server with priority 0 was configured for the category of the NZBs that did not download.

Could you see if setting the Category to only Default for both servers makes a difference?