Scheduled jobs that silently never ran
The reminder, notification and weather jobs had stopped running for at least a week. No error appeared anywhere, and homeowners simply stopped getting reminders.
Why it was hard, what I decided, how AI helped
- Why it was hard
- Vercel's Hobby plan caps how many cron jobs a project may register. The project declared three, and Vercel registered none of them without saying so. An earlier fix had addressed the frequency limit but not the count limit.
- My approach
- An audit I had run on the new admin console found the gap: zero cron calls in the production logs, and the newest notification was seven days old. I wanted a fix that could not come back when a plan or limit changed.
- How AI helped
- Claude Code collapsed the three schedules into one daily route that runs each job in turn, recorded every run in a cron_runs table, and showed scheduled-job health on the admin console.
- The decision
- One schedule, not two, because one is inside every plan's limit. A job that has never run had to show up as a row, not be missing, because missing reads as 'no such job'.
- Evidence
- PR #46 · commit eeec476 · migration 042 · tests/production-readiness/cron-routes.test.ts





