Retention limit not working?

Hi Guys,

I have recently installed NZBDrone (Migrating from Sickbeard). The issue I’m having is that on snatching new files it does not seem to be honouring the retention limit sent in the indexer setting page.

I have it set to 1100, but it is snatching files exceeding that, for example when I look in SABNZBD I am seeing files in the range of 1200-1500+, because of this the files are failing…

Am I being silly on doing something wrong? I’m using the latest windows version from the webpage.

Further, and slightly off topic, why when I look at the series are some of the downloaded quality icons blue instead of black?

If you do a manual search for that episode does one of your indexers return the age as less than 1100?

They’re currently blue when it’s a proper/repack release.

Hi Markus,

In history the release it snatched shows 3.3 years, i.e. circa 1200 days. Searching manually on the indexer website shows the same thing…

Thanks, I’ll take a look and let you know if I have any more questions on it.

Added to Trello for tracking: https://trello.com/c/bWVNtxxz/579-check-that-retention-spec-is-working

My tests show it working correctly. I set it to 10 days and it blocked a release from about 12 days ago, but one from 2 days ago was accepted.

It’s not working for me…

These are the steps I’m taking.

Enable monitoring on a season I’m missing, this enables the ‘missing shows’, from there I select an episode and select ‘search selected’, it then grabs episodes of various ages exceeding the retention limit. Perhaps this kind of search does not respect the retention limit setting?

No, all searches verify the retention is within the configured limit, RSS Sync does it as well.

If you do a manual search you will see the red exclamation mark when the the release exceeds your configured retention. Have you verified the retention was saved properly after it was entered?

If you enable trace logging and perform a single search it will log what the retention is set to and again if the retention is exceeded.

I think I’ve made progress.

Using the manual search I can see that Usenet Crawler reports the file in question as 401 days old, the problem is that SABNZBD shows the file as 1206 days, so there is a mismatch somewhere, is it possible we’re picking up the wrong details from Usenet Crawler, or even that they are reporting the wrong information?

I guess either is possible, but more likely the info coming back from usenet-crawler is wrong.

If you enable trace logging you can see the URL drone requested, if you put that into your browser it will give you the XML response. drone uses the publish date of the item to determine the age.