Vercel's built-in cron triggers your serverless functions on a schedule. For simple use cases it works. But it has no failure alerts, no execution history on the Hobby plan, and no way to know whether your function actually completed successfully — only that it was called.

Where Vercel cron falls short

Vercel cron works by invoking one of your API routes on a schedule defined in vercel.json. The invocation is fire-and-forget — if your function times out, throws an error, or returns a non-2xx status, you get no alert. You find out when a user reports something is broken.

The specific gaps developers run into:

• No failure alerts. Vercel does not send an email or webhook if your scheduled function fails.
• No execution history on Hobby. The free plan does not retain cron execution history.
• Timeout ceiling. Functions are subject to the same timeout limits as all serverless functions — 10 seconds on Hobby, up to 300 seconds on Pro.
• HTTP-only. Vercel cron calls an HTTP endpoint on your app. You cannot schedule arbitrary background work outside your deployment.
• No heartbeat monitoring. Even if your function is called successfully, you have no built-in way to verify it completed its work — only that it was invoked.
• Minimum 1-hour interval on Hobby. Sub-hourly schedules require a paid plan.

If you are hitting any of these limitations, you need an external tool.

Comparison at a glance

Tickstem — cron + heartbeat + uptime in one API key

Best for: developers who need scheduling, failure alerts, heartbeat monitoring, and uptime checks without managing multiple tools.

Tickstem is an external HTTP cron scheduler with built-in monitoring. You register your Vercel endpoint as a cron job, and Tickstem calls it on your schedule — every minute if needed, regardless of your Vercel plan. You get email alerts when a job fails or times out, full execution history, and response assertions to verify your endpoint returned the right status code.

Where it goes further than a simple cron service: Tickstem includes heartbeat monitoring. Your function pings a unique token URL at the end of each successful run. If the ping stops arriving within the expected window, you get alerted — catching cases where the function was called but silently failed partway through.

# Register your Vercel endpoint as a cron job
curl -X POST https://api.tickstem.dev/v1/jobs \
  -H "Authorization: Bearer $TICKSTEM_API_KEY" \
  -d '{
    "name": "nightly-sync",
    "schedule": "0 2 * * *",
    "endpoint": "https://your-app.vercel.app/api/nightly-sync"
  }'

Free tier: 1,000 executions, 5 uptime monitors, 5 heartbeat monitors per month.

Upstash QStash — reliable delivery with retries

Best for: developers already using Upstash who want guaranteed delivery with automatic retries.

QStash is a message queue and scheduler designed for serverless environments. You publish a message with a delay or schedule, and QStash delivers it to your endpoint with automatic retries on failure. It integrates naturally with the Vercel ecosystem.

It does not cover heartbeat monitoring or uptime checks — it is a scheduling and delivery layer, not a monitoring layer. Good choice if retry semantics matter more than observability.

Inngest — complex multi-step background jobs

Best for: multi-step workflows with fan-out, conditional logic, and event-driven triggers.

Inngest lets you define background functions in code and trigger them on a schedule or in response to events. It handles retries, concurrency, and step functions — things that are difficult to build reliably in a stateless serverless environment. First-class Vercel and Next.js integration.

The tradeoff is complexity. Inngest requires adding their SDK and restructuring your background work as Inngest functions. For simple "call this endpoint on a schedule and alert me if it fails," it is more than you need.

cron-job.org — simple external cron, free

Best for: plugging the scheduling gap with zero added complexity.

cron-job.org is a free external cron service that calls your URL on a schedule. Basic email alerts on failure, execution history retained. No SDK, no heartbeat monitoring, no uptime checks.

For developers who just need the scheduling gap filled without adding any infrastructure complexity, it is the lowest-friction option.

How to choose

• Just need sub-hourly scheduling and basic failure alerts: cron-job.org covers the basics for free.
• Need scheduling + know when the job actually completed its work: Tickstem — heartbeat monitoring is the missing piece Vercel does not provide.
• Need reliable delivery with retries and already use Upstash: QStash fits naturally into that stack.
• Building complex multi-step background workflows: Inngest is built for that use case.
• Need cron + heartbeat + uptime without managing three tools: Tickstem bundles all three under one API key.

The pattern worth avoiding: starting with Vercel's built-in cron, adding cron-job.org for alerts, and eventually needing heartbeat monitoring — ending up with three separate tools and three places to check when something breaks.

Originally published at tickstem.dev. Also worth reading: Why cron jobs fail silently on serverless platforms.