SABnzbd Forums

This is a small window use case, but it happened to me.

While a very large job was being repair/unrared, I saw the warning that i had orphaned jobs.
So i clicked and told it to clean them.

Unfortunately, it deleted (folder and all) the currently processing one as well, causing it to fail.

Yes I also noticed this.. Shypike can you fix this in the python code?

Jumbs wrote:This is a small window use case, but it happened to me.

While a very large job was being repair/unrared, I saw the warning that i had orphaned jobs.
So i clicked and told it to clean them.

Unfortunately, it deleted (folder and all) the currently processing one as well, causing it to fail.

How did you delete the items? One by one?

Used the mass delete.

After i clicked it i realized i saw the currently unraring piece in the list.

Shypike: the mass delete is just a for loop over all the single orphaned downloads, so doesn't matter how he deleted. It just shouldn't be in that list..

Jumbs wrote: After i clicked it i realized i saw the currently unraring piece in the list.

Right, the current post-processed job should not be in the list at all.
Under investigation.

Problem will be solved in Beta2.
(Fixed in the source on github)