infrastructure//Vercel//cron jobs

Cron jobs are scheduled Vercel Functions that run at fixed intervals, defined in `vercel.json` with cron syntax: Vercel's form of the general cron job. They serve daily reports, cache warming, periodic API syncs and cleanup tasks.

Cron jobs are scheduled Vercel Functions that run at fixed intervals, defined in vercel.json with cron syntax: Vercel's form of the general cron job. They serve daily reports, cache warming, periodic API syncs and cleanup tasks.

They share the timeout limits of regular Vercel Functions (10 s, 60 s or 300 s depending on the plan). The minimum interval is one minute on Pro and once a day on Hobby.

For recurring batch work (syncing emails every hour, updating analytics daily) they are simpler than Inngest or Trigger.dev: there is no queue infrastructure, only a function on a schedule.

A batch that exceeds the timeout fails in a cron job exactly as it would in a regular function. Heavy batches combine the two: the cron job triggers the work and Inngest or Trigger.dev processes the queue.