Accidentally set nzb to 'Stop', need to resume

[dir]

I mis-interpreted what "Stop" means as a priority.

I had a 48GB nzb downloading and reached 25%. I wanted to lower its priority to let another nzb complete, then decided I didn't want it running right now as its not that important, so I set it to 'Stop'.

The other nzb started up and finished quickly, but sabnzbd then moved the large nzb to the History list as a "» Repair failed, not enough repair blocks (1824 short) ". Hitting Retry simply made sabnzbd try to repair it, which of course failed.

I had expected the "Stop" priority to mean "don't do anything more with this nzb" and would have left it in the queue, and simply not continue downloading it, but instead it basically ruined it.

I've searched the FAQ, Wiki, and this forum, and can't find anything explaining what this "Stop" priority means and how to use it correctly. There also doesn't seem to be any way to resume an NZB that's been moved to the History queue. I have worked out how to do that the manual way, so I don't need that explained to me, but I have a few questions:

- What does 'Stop' mean as a priority - from its behaviour, I guess its a way to tell sab not to continue downloading an nzb in mid-stream, but this seems like a fairly obscure requirement
- Is there any way to 'Suspend' an nzb while letting others run (I don't want this huge one using up my bandwidth except for when I'm in bed, but I still want my normal TV show stuff to come in as usual)
- Is there any function in sabnzbd to allow resuming an nzb thats been moved to History ( again, I know how to do this manually, I'm hoping there's a function that I can click on that simply moves it back up to the active queue and continues where it left off)

[shypike]

Stop send a job to the post processing queue immediately.
People use it to get rid of stuck jobs (often dur to server issues).
Retry will usually download the rest of the job.
Unless the job couldn't have been completed anyway,
What happens if you set SABnzbd to paused and retry the job.
The queue details (click on the item) should show what still needs
to be downloaded.

[dir]

Retry didn't put it back in the queue, it simply tried to unpack it again and failed. If it had moved it back up to the queue it would certainly have continued. Its too late to try pausing and retrying the job. The queue details showed that it needed another 75% of the parts required.

There's absolutely nothing wrong with the nzb. Nothing. Its perfect. I simply stopped it then when it moved to the History list, I clicked on 'Retry' and it tried unpacking again instead of moving back up to the active queue.

Since I did all that, I started the download again but have selected only the missing parts (part 26 through 100), and its been happily downloading those since then. I fully expect that I will be able to manually unrar/par the collective set of parts once this has finished.

[shypike]

Are the files now divided over two temp folders?
If so, SABnzbd isn't clever enough to join those.

You are right about SABnzbd not trying to download missing files,
because it considers the missing files to have been removed by the user.
In this case the best remedy would have been to
remove the failed item from History without deleting files.
Next step: recover the item from the orphan list on the Status page.
It would have worked then.
Obviously, you could not know this. Sorry about the incorrect advice.

[dir]

I think this is going off on a problem-solving tangent. I don't need help sorting out the nzb, I simply wanted to know answers to some questions:

- (first question answered, thanks)
- Is there any way to 'Suspend' an nzb while letting others run (I don't want this huge one using up my bandwidth except for when I'm in bed, but I still want my normal TV show stuff to come in as usual)
- Is there any function in sabnzbd to allow resuming an nzb thats been moved to History ( again, I know how to do this manually, I'm hoping there's a function that I can click on that simply moves it back up to the active queue and continues where it left off)

[shypike]

- Is there any way to 'Suspend' an nzb while letting others run (I don't want this huge one using up my bandwidth except for when I'm in bed, but I still want my normal TV show stuff to come in as usual)

Yes, just set it to paused. The arrow in front of the job.
You can also use low priority so that it is moved to the end of the queue.

- Is there any function in sabnzbd to allow resuming an nzb thats been moved to History ( again, I know how to do this manually, I'm hoping there's a function that I can click on that simply moves it back up to the active queue and continues where it left off)

That's what Retry is supposed to do.
There's only one shortcoming. Missing parts of files will not be filled, only full files.
In retrospect, I find it odd that the Stop didn't work properly.
Just tested it again, and in my case it does resume properly.

[dir]

Good to learn about the suspend - I hadn't realised the 'play' vs. 'suspend' function of that arrow.

I'm trying a 'stop' on an nzb that's 98% complete. It moved it to History and started processing it. I saw it at "Verify" then as I was typing in this reply, I checked again and its now back at the top of the active queue. Is this normal behaviour? It seems to make "stop" really a "try to process what's available, and continue/resume immediately if need be". Which I suppose makes sense except that the word "stop" is a bit misleading.

I guess I'm simply not up to speed on how to interpret some of the functions and workflow of sabnzbd.

Thanks for the help and explanations.

[shypike]

"Stop" was introduced when we had issues with jobs stalling
at 99% either due to server issues or bugs in SABnzbd.
It was easier to do than adding a stop button.
It's not documented properly. Not that most people read the Wiki