SABnzbd Forums

shypike wrote:We can reproduce it and are close to the solution.

That's very good to know. Thanks for all the help.

Why does one get orphaned jobs? I had three orphaned jobs just now but I swear I've deleted those manually from the queue yesterday.

Same cause. We'll have it fixed in release 1.0.1

shypike wrote:Same cause. We'll have it fixed in release 1.0.1

Gotcha. Thanks.

I see in the changelog of the latest version that this issue is supposed to be fixed. Recently, Sonarr just downloaded a sample file and had to manually delete it from Sonarr's history again. Same thing happened in Sab, it got deleted from its history but the files (being they're saved in the completed folder) remained there. Any thoughts?

There's still the issue that SABnzbd API sometimes lists the wrong job status.
That will be fixed in 1.0.2

I think kevindd992002 means that he expects that when a Completed (so *not* Failed!) job is removed from SABnzbd's history, the Completed files should also be removed.

And that is not going to happen, like said before. But what should work is when you delete a Failed job that all files should be removed.

Isn't Sonarr confused by the "Deleted" status?

Based on the history of thread, I thought that when completed itemd are deleted by a third-party app with the "delete" API call set to 1 or something, then it will push through with the deletion? At least tgat's how I understood some of the replies above.

No no, Sonarr is not confused. There are times that a certain release is a sample, so in Sab the download would complete but in Sonarr it will stay unprocessed because it is recognized as a sample. So I have to manually delete those from Sonarr's queue which in turn would successfully delete them from Sab's history but thw files will remain as they are in the completed download folder.

kevindd992002 wrote:So I have to manually delete those from Sonarr's queue which in turn would successfully delete them from Sab's history but thw files will remain as they are in the completed download folder.

That's not new, SABnzbd has never deleted completed files and it never will.
This is a conscious choice: we wouldn't want a bug on our side to wipe out your media collection.

So I take it that your reply I misnterpreted your reply here? http://forums.sabnzbd.org/viewtopic.php ... 15#p105300

Before that post, I explained the same situation and you replied regarding the delete api call parameter which I assumed that, if included, will delete files from the completed download folder as well.

The "delete" parameter is only useful for "failed" jobs and applies only to the part in the temporary download folder.

The problem is that Sorting, user scripts and tools like Sonarr may do all kinds of things with the final files.
We simply don't want to mess around in your media collection.
By default, we don't even overwrite existing files, but rename the new ones.

Ok, got it. Thanks for the clarification then.

I got another instance of the failed download not being deleted from Sab's history issue. It was "aborted, cannot be completed" by Sab, then Sonarr requested Sab to delete it from the queue, but Sab did nothing. I can still see the failed download in Sab's history. Any thoughts?

What is visible in SABnzbd's logging?