Hi, I am attempting to create a cron job. The cron job I created correctly shows up on my Vercel dashboard. But the cron job does not run at the scheduled time. Instead, it only runs once I start building a new build. That probably sounds weird, but I’ve tried four times and every time the cron job …

Hey @for-ry-in-range , Most likely the logs won’t show up since the function you’re executing through your cronjob is cached. The cron job will always run according to it’s schedule, but if it hits an endpoint that’s cached then it won’t show. Cron jobs don’t have the ability to completely bypass t…

Hi @for-ry-in-range . It looks like there might be a problem with your cron schedule. You can use a tool crontab guru to validate your cron expression.

@amyegan I had already used the crontab guru to validate the time. Also, I know the cron job can run within a one hour window of the time given. I’ve waited for the whole hour and the cron job does not run, until I start a new build. What else do you recommend I try?

@amyegan Oh I just realized my schedule was missing “* *”, which is why you thought there was a problem with the cron schedule. I think I accidentally deleted part of the code after I pasted it into the forum. But my actual code is “35 4 * * *” :smiley:

That schedule makes more sense! If you try to run the /api/cron function directly and then try to click the Run button in project settings to manually run the cron job. What happens in each of those scenarios?

When I run /api/cron in Postman, nothing happens. And when I click the Run button, the log shows status=200. But the code in /api/cron still did not run. So then I tried starting a new build, and then the /api/cron finally ran.

It seems like there’s a problem with the function itself if nothing happens when you run it with Postman or the Run button. I recommend looking into what’s going wrong with the function. The Deployment Summary will tell you more about the functions that were deployed. And Runtime Logs can help you …

The /api/cron function does correctly show up in the Deployment Summary. The Runtime Logs show that the GET request to /api/cron went through successfully for BOTH the call from Postman and the call from the Run button, even though the code in /api/cron did not run. What else should I try? Thanks!

Since the functions at least attempt to do something, I suspect there’s a silent error or a flaw in the return data. Using try/catch and console.log() is probably the simplest way to gather more info about what’s happening inside the function.

import { inngest } from "../../../../inngest/client"; export async function GET() { try { await inngest.send({ name: "myfunc/send-summary" }); console.log("Cron worked") return new Response("Successful!", { status: 200 }); } catch (error) { …

Hi, @amyegan are you still there?

Cron Job Not Running

Help

for-ry-in-range (For Ry In Range) August 22, 2024, 4:32pm 17

It works now after adding export const dynamic = 'force-dynamic'

Thank you so much for your help!

3 Likes

Topic		Replies	Views
Cron Job not executing Help cron-jobs	3	349	December 22, 2024
Cron Jobs Not Executing on Vercel Despite Configuration AND Lack of Logs + Troubleshooting Help	4	366	November 29, 2024
Cron Jobs Not Executing on Vercel Pro Plan Despite Configuration and Troubleshooting Help cron-jobs	9	281	November 18, 2024
Cron Jobs Not Registering - Platform Bug with vercel.json Updates Help	2	104	August 3, 2025
Cron Jobs Not Running Help nextjs , cron-jobs	9	286	February 23, 2025

Cron Job Not Running

Related topics