I’ve just started using Sonarr and for some reason I can’t get failed download processing to work. I’m getting a couple of different behaviours, neither of which seems correct to me!
If the download fails with a ‘Repair failed, not enough repair blocks’, I get a yellow tray icon on the activity queue and a mouseover saying no files are eligible for import. If I go to the calendar or the missing list I get a full purple bar suggesting they have been 100% downloaded.
If the download fails because it is out of retention, I get the red cloud icon saying that the download has failed and the error ‘Download wasn’t grabbed by sonarr, skipping’ eventhough the download was grabbed by sonarr!
In neither case is the release blacklisted, nor automatically searched for again. I have got the debug log turned on, but figured this was likely some relatively easy configuration issue. If it helps, I noticed that when I added a season for monitoring it didn’t automatically start trying to find the missing episodes either.
Make sure you have a matching category in Sabnzbd, otherwise the API will discard the items in the SABnzbd history.
You can check the applied category in the main view (first drop-down next to the “time left”)
Also, make sure you don’t have the download directory set as the drone factory directory in Sonarr. It will conflict with the failed download handling.
Thought that was going to fail and was going to show screenshots of the Sonarr end, but it didn’t! Could it be something in the SABnzbd settings? These are my postprocessing settings…
One from the episode list to show that the progress is being correctly pulled into Sonarr (though oddly enough no in the queue, only on the show list).
Unpacking can fail for numerous reasons, offhand I believe Sonarr does not handle these as failures because it could be related to disk space not a bad download.
This means the ID that SAB returned to Sonarr when it was added to SAB has changed, the switch Check before download (check your settings to make sure this is not enabled) in SAB will do this as will manually retrying the failed download in SAB.