Skip to content
Did It Run?
Start Free
← Blog

Vercel Cron Jobs can skip a run and leave no log

Running a scheduled job with Vercel Cron Jobs? Vercel's own docs list a few ways it can go quiet:

  1. Delivery is best effort. A transient network error can stop a run from reaching your function, and then "no runtime log is created for that scheduled run."
  2. Failures aren't retried. "Vercel will not retry an invocation if a cron job fails."
  3. Redirects end the job. Cron doesn't follow a 3xx, and redirected or cached responses don't show in the logs.
  4. Hobby timing is loose. 0 8 * * * can fire anytime from 8:00 to 8:59.

(Vercel: Managing Cron Jobs)

So "no errors in the logs" can also mean "it never ran." Have the job ping a heartbeat when it finishes, and a missing ping becomes an alert.

Get your ping URL free, 3 watches included.