New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Scaling a worker fleet from one replica to three quietly turned one nightly invoice email into three, and support caught it before anyone else did.
What you'll have at the end
One scheduled job dispatched exactly once per tick, proven by scaling workers to three and counting the runs
You need
A scheduled job that already ticks correctly at one replica, running inside a worker fleet you can scale up and down, plus a fast shared store your app already reaches for other short-lived locks or cache keys.
Not covered
Keeping the schedule alive through the minutes when every replica restarts together during a full redeploy; this only stops one tick from being claimed by more than one replica that is already running.
Leans on
Schedule a job that survives a redeploy
for keeping the schedule alive through the redeploy window itself, when every replica restarts together and the job briefly has nobody ticking for it at all.
Survive a cache stampede under load
for the same set-if-absent claim protecting a cache key from a stampede of readers instead of a scheduled tick from a fleet of replicas.
Checked 19 Aug 2026
Part of the Background Job Processing Systems cookbook