Vercel Cron Jobs run your functions on schedule, but won't alert you when they fail. Add one line to get instant notifications.
Serverless functions have execution limits. If your job exceeds them, it's killed mid-execution with no alert.
Edge cases during cold starts can cause functions to fail before your code even runs.
If your function throws an unhandled error, it fails. Vercel logs it, but doesn't notify you.
Cron jobs on Hobby plans are limited. Even on Pro, monitoring isn't built in.
Add a fetch call at the end of your cron function:
// Next.js App Router example
export async function GET() {
// Your job logic
await generateDailyReport();
await sendEmailDigest();
// Ping CronSignal on success
await fetch('https://api.cronsignal.io/ping/abc123');
return Response.json({ success: true });
}Vercel triggers your cron function on schedule
Your business logic runs. If it throws, the ping never happens.
CronSignal expects a ping on schedule. No ping? You get an alert.
{
"crons": [
{
"path": "/api/cron",
"schedule": "0 9 * * *"
}
]
}Use the same cron expression in CronSignal. We'll expect a ping within your configured grace period.
Use fetch() — it's globally available in Node 18+.
fetch() is native to Edge. No additional setup needed.
Use the same cron syntax as your vercel.json. We understand standard cron format.
Email, Slack, Discord, Telegram, or webhooks. Know when functions fail.
Monitor all your Vercel cron jobs for one flat price.
Know immediately when functions fail. 3 checks free, no credit card required.
Start Monitoring FreeTakes 2 minutes to set up