Support Forum

Thanks Shypike. Now that I know it's not a simple switch in my settings I'll do my own investigation and report back here in case anyone else uses this feature and has a similar problem in the future.

I set up a test resume, that was successful, and the differences in the logs is interesting: Unsuccessful resume never initiates the connection (scheduler was set to resume low priority downloads at 11:30 last night): http://i.imgur.com/pg1ArFT.jpg This was a test resume I scheduled for 9:30 this mo...

EDIT: OS is Windows 10 Pro, SAB Version is 1.0.3 [927ba3c] I had originally posted this problem in the beta area because I was playing with release 1.1.0 beta 1; in my investigation I decided to roll back to stable, to see if the issue persisted there or not and it does. I finally have the right log...

Mine is also occasionally doing this on the last PAR2 file. Manually pausing, then resuming the job allows it to finish. I've not been able to nail down exactly why it does it nor have I been able to positively reproduce it.

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 ...