From 3a4805ba88f97bae0ed41765de513b5f49627eb7 Mon Sep 17 00:00:00 2001 From: Mark McDowall Date: Mon, 4 Nov 2013 10:39:38 -0800 Subject: [PATCH] Added failed download handling --- Failed-Download-Handling.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Failed-Download-Handling.md diff --git a/Failed-Download-Handling.md b/Failed-Download-Handling.md new file mode 100644 index 0000000..c710a28 --- /dev/null +++ b/Failed-Download-Handling.md @@ -0,0 +1,22 @@ +Failed downloading currently only works with SABnzbd + +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: + + 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 Media Management) 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 \ No newline at end of file