All modules
MODULE 10 · WORK NOBODY WAITS FOR
Background jobs
If a user is waiting, it's not a job.
Reports, bulk email, nightly syncs — work that outlives a web request. It needs somewhere to run (a scheduler on your backend), a record of every run, and a plan for when it fails at 2am.
WHEN YOU NEED IT
Tier 2–3, when route handlers start timing out or work must run on a schedule.
THE CHOICE, PER TIER
- T2Cron on the backend host, jobs table for history
- T3+ queues and retries for heavier work
SAY THIS TO YOUR AGENT
"Add a scheduled job runner to the backend. Every run writes a row — started, finished, failed — and failures alert me instead of failing silently."
DONE WHEN
- Jobs run on schedule without a user involved
- Every run is recorded and inspectable
- A failed job tells you, not your users