Abort jobs that cannot be completed - wrong folder
Posted: May 1st, 2020, 10:09 am
If I enable "Abort Jobs that cannot be completed" SabNZBd leaves everything in my download_inprogress folder. If I disable it, then it fruitlessly tries to complete the download, eventually fails, and moves it to the "download_completed" folder - as expected.
There are a couple of issues with this: First my download_inprogress folder is HUGE full of failures. Second, my failed-download post-processing doesn't work. As it doesn't look in download_inprogress.
I need these aborted downloads to be treated the same way as failed downloads - which is to move them to completed so that post-processing detects the failure and retries.
Any ideas to resolve this aside from leaving the feature disabled? This is the only way I can get failed downloads to be handled and retried - but wastes time and bandwidth.
There are a couple of issues with this: First my download_inprogress folder is HUGE full of failures. Second, my failed-download post-processing doesn't work. As it doesn't look in download_inprogress.
I need these aborted downloads to be treated the same way as failed downloads - which is to move them to completed so that post-processing detects the failure and retries.
Any ideas to resolve this aside from leaving the feature disabled? This is the only way I can get failed downloads to be handled and retried - but wastes time and bandwidth.