I am getting an episode getting downloaded multiple times granted this one did download then a proper was released so it grabbed that
however it grabbed a proper again and downloaded a second time so i now have this
both episodes were grabbed from the same indexer
hopefully just a one off but thought it was weird and wondering if anyone else has got this either on this episode or others
Its because the file name doesn’t contain proper. Though it should have been caught by a change made within the last 2-3 weeks
What version are you running/what branch? Seems yours is out of date as I tested this release and its working as expected (takes the quality from the folder name instead of the file name)
Currently Mine is Develop Branch
NzbDrone Ver. 2.0.0.981
Same build for me, but it worked fine, even when I tested it. How did you stop it from happening a 3rd time?
i didn’t in fact i just checked my sabnzbd queue and look what has happened
Well, first off, I’d recommend turning dupe check on in SAB, and secondly, is it still happening now?
I’ve added a bit more trace logging to the import process to track the quality a bit better, I’m not able to reproduce this issue with the same release and without trace logs I don’t see a way to get an idea as to what is going wrong here.
I just checked sab and the dupe check was enabled as i thought it was before checking it was set to pause dupes but i have changed it to discard as it obviously did not pause anything so that wasnt working
it has not happened again in several hours hopefully whatever was causing it has corrected itself but i will let you know if it happens anymore with either that same episode or with any whatsoever
i checked and they were being grabbed from different indexers so cannot say it was a indexer issue
hey if you dont know very unlikely i am gonna figure it out 
The issue is the release name (nzb name) contained PROPER, so it was grabbed, but the file inside the rar set (and once extracted didn’t).
This issue was reported before and to fix it, we take the quality of the folder into consideration when determining the file’s quality. Since the folder should have been the same as the release name (included PROPER) it should have been used instead of the quality of the file itself which was SDTV w/o proper.
I don’t know why this new process worked for me, but not for others (received one other report of this, via IRC).
To the OP, what version of sabnzbd are you using? I had this same problem in the past on couchpotato and it turned out that it was caused by having a really old sab version (was 6.xx something) which would cause weird issues with API calls etc.