Scheduled and triggered job runs start on time when another run's server is slow to respond

The scheduler now starts a run that is due without first waiting for replies about other runs. Previously, while a server did not answer about a run already in progress, every other job's next run could start 10 seconds or more after its scheduled time, or after jobs.trigger was called.