loading entry…
loading entry…
vercel.json cron entry like */5 * * * * (every 5 min) is accepted in dev but the production deploy emits a build warning and the cron never runs.
Vercel Hobby tier allows cron schedules at daily granularity only. Sub-daily schedules require Pro.
Two options:
curl from a separate scheduler (Hetzner cron, GitHub Actions on a schedule, an Upstash Q-job). The Vercel function stays; only the trigger source moves outside Vercel.For Mission Control's /api/health 5-min cron, use the external-trigger pattern: a small cron on the Hetzner VPS curls the endpoint every 5 minutes.
~/.claude/playbooks/nextjs16-vercel-deployment.md