When waking from sleep, missed scheduled jobs start running before the network is fully available. My machine is connected to a docking station and it takes a while for the network adapter in the docking station to get connected.
I found the post that was solved by adding a 30 second delay. Unfortunately that 30 second delay is not long enough for my machine.
Can the scheduling delay be made configurable?
This delay is not configurable in the current version. I’ll add an option in the next update.
Did the configurable delay make it into any Web release? I have the same issue after waking from sleep (“no such host” error), and I didn’t see any way to configure the delay amount with version 1.5.0.
Edit: Nevermind, I see it is still on the roadmap todo list.
Delay is the wrong solution here anyway. The correct solution would be to test for connectivity and start backup when the destination is reachable.
You can implement that today in pre-backup script easily, no need to wait for the feature that won’t properly solve the problem anyway.