1
0
Fork 0
mirror of https://github.com/Sonarr/Sonarr synced 2025-03-14 16:11:23 +00:00

Fixed formatting on failed download handling

Mark McDowall 2014-03-21 20:18:59 -07:00
parent 7d1fa94aa6
commit f450e41e2f

@ -4,19 +4,20 @@ There are a couple components that make up the failed download handling process:
1) Check SABnzbd Queue and History for failed downloads
1. Queue - Encrypted (passworded) as detected by SAB
2. History - Failed, whatever the reason, not enough to repair or extraction failed
When drone finds a failed download it starts processing them and does a couple things:
a. Queue - Encrypted (passworded) as detected by SAB
b. History - Failed, whatever the reason, not enough to repair or extraction failed
1. Adds a failed event to drone's history
2. Removes the failed download from SAB to free space (opt out)
3. Starts searching for a replacement file (opt out)
When drone finds a failed download it starts processing them and does a few things:
1. Adds a failed event to drone's history
2. Removes the failed download from SAB to free space (opt out)
3. Starts searching for a replacement file (opt out)
2) Blacklisting
Allows automatic skipping of nzbs when they fail, this means that nzb will not be automatically downloaded by drone ever again (You can still force the download via a manual search).
There are 3 advanced options (on Download Client) that control the behavior of failed downloading in drone, at this time, they are all on by default.
Enable - Turns the checking of SAB and the blacklist functionality on or off
Redownload - Controls whether or not drone will search for the same episode after a failure
Remove - Whether or not the download should automatically be removed from SAB when the failure is detected
Enable - Turns the checking of SAB and the blacklist functionality on or off
Redownload - Controls whether or not drone will search for the same episode after a failure
Remove - Whether or not the download should automatically be removed from SAB when the failure is detected