SABnzbd Forums

EDIT: This is still hit or miss and I'm not able to reproduce in exactly the same way every time, working on a better scientific process, I'll post back once I have something more concrete.

Version: 1.1.0Beta1 [6f65d47]
OS: Windows 10

Steps to Reproduce:
1. Have scheduler set to pause low priority jobs
2. Add low priority job to queue (should be paused)
3. Have scheduler resume low priority jobs
4. Job will resume/unpause but will not begin downloading until user manually pauses, then resumes job.
5. Rest of queue will download fine once user has paused/resumed first job in queue.
6. Any new downloads added to queue with normal priority download fine. Only seems to affect jobs that would be affected by scheduler (in this case, low priority jobs)

Is it possible this is a setting somewhere? Is the pause/resume low priority jobs new with this beta? Just discovered it, but only recently looked for it because of a specific need as of late to not kill my connection during the day for old backfills.

I've tried restarting, I've tried rebuilding the queue, I've tried clearing the queue than re-adding one job at a time to try and diagnose this.

We have had some reports about jobs hanging at the end.
Most issues have been resolved, but their could still be a bug hiding.
You probably should concentrate on the hanging and not the relationship with the scheduler.
We would love to get a reproducible scenario from you
and like to help you where we can.