![]() ![]() ![]() Could there be implemented a function that communicates with sabnzbd's API for whenever there's a "» Aborted, cannot be completed" or whenever a fail message appears, try the next darn NZB just in case? :shock. You can check the applied category in the. Make sure you have a matching category in Sabnzbd, otherwise the API will discard the items in the SABnzbd history. I'm getting a couple of different behaviours. I've just started using Sonarr and for some reason I can't get failed download processing to work. The unit had to restart after power loss and now has 130Gb of rar and par files waiting for the SABNZBD. Hi, I am using SABNZBD on my NVX pro pioneer. ![]() So I get a lot of downloads that "fail" in SabNZBD but if I come like 8 hours later and hit "retry" magically they finish just fine. Configure Sabnzbd to retry failed downloads automatically by grabbing a new release from your indexer. Another reason might be because you think the failure. Because you may have various servers enabled/disabled at any given moment It would be nice to be able to send a file back to the Queue and actually have it retry downloading the missing blocks after you've enabled any servers that were disabled. Sabnzbd fails to restart in in 2.0.0Alpha1 on Windows when triggered from Glitter. SABnzbd will skip each files that has already been downloaded and then proceed to download the. If you now have a larger NZB with either more RAR files or just more PAR2 file, click Retry and enter the new NZB in the dialog. If it's just a case of a full destination disk, click Retry. A failed job will have an entry in History. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |