SABnzbd Forums

All my indexer scraped downloads are by default set as 'pause' (too much pollution, so I want to manually okay them), however as of recently, when I press the resume button, the download is checked for consistency, then paused again and moved to the bottom of the queue. Was wondering why they never appeared in the 'completed' list, and then I found them on the very last page...

Previously, the consistency check would be done, then immediately followed by the full download (if the job was deemed intact), and additionally the job was left it in its existing position in the queue.

I assume default behaviour changed somewhere in the most recent version? How do I restore this previous behaviour?
Or have I found a bug (in which case feel free to move this thread)?

Well, I indeed removed that code in a refactor.
I will see if I can restore it.

Will be fixed in 3.1.0.

It's not me then, thanks

3.1.0 is out, so try if it fixes things for you

Installed! The queue position isn't changing anymore for individual jobs, but I'm afraid it's still (re)pausing them after clicking 'resume' and running the quick check.
I've not changed any settings for quite a while now (except for adding and editing RSS search queries), but is there perhaps a setting I should toggle?

To make sure: you add them paused, click resume, but then after checking they come back paused?
I might have an idea what could be going wrong.

safihre wrote: ↑October 19th, 2020, 8:40 pm To make sure: you add them paused, click resume, but then after checking they come back paused?
I might have an idea what could be going wrong.

Exactly! For completeness' sake:

• the RSS config to which the search query belongs, has 'Paused' specified as the default priority (and each search query has 'Default' set)
• new jobs are automatically in queue as paused
• I press 'resume' on one of them
• SABnzbd does the integrity check
• pauses it again

The queue position of the repaused job is now retained though, that was fixed in the update.

Another check: the category that you use for this job, does it maybe also have the Paused priority set?

It does! I guess in the most recent versions it applies said pause a second time?

Yeah that's indeed what happens. The Category-parsing happens again when it is re-added because we basically throw away the whole job and re-add it after a pre-check. So we need to apply all the same settings again.
Not sure if I can easily fix it.. :/
Removing the paused priority from the category will fix it I think, then the RSS will still add the job paused but it won't pause again after the check.