Consider latency when getting next send time from DB.

4 jobs for !1671 with 2336-get-next-send-time in 9 minutes and 49 seconds (queued for 4 seconds)
latest merge request