Daily note
The clock keeps going while the queue fills
Scout now catches up elapsed scheduling minutes; the db3 Cloud plan adds optional compute scale-to-zero.
Scout’s scheduler now catches up every elapsed minute, including time spent inserting jobs into the queue. Slow queueing can no longer make it skip the next scheduled minute. Each job retains its original due time, and saved progress allows catch-up to continue across restarts.
Scheduler catch-up
Slow queueing must not skip scheduled work.
Evaluate every elapsed minute, keeping each job attached to the time it was due.
12:00 · scheduled
Ten jobs become due
Each keeps its 12:00 scheduled time, even while queue insertion takes longer.
13 seconds per enqueue
The clock moves on
The controlled test advances through 12:01 and 12:02 while the first batch is queued.
Catch up elapsed minutes
Pick up the later jobs
Evaluate the intervening minutes rather than jumping straight to the current minute.
12 jobs queued once. All 12 completed.
The fix was committed, pushed and deployed. A controlled-clock test simulated thirteen seconds per enqueue: ten jobs due at 12:00 and two due in subsequent minutes were each queued once and completed against a real database and queue. Live checks confirmed the deployed release, advancing scheduler progress and both worker lanes completing checks. A hard crash between claiming and enqueueing a job still needs reconciliation.
The db3 Cloud product plan now includes Cloudflare networking and optional compute scale-to-zero. This remains a proposal: waking web processes is only part of the design; scheduled work, durable uploads and database availability need their own lifecycle.