Cron Jobs stopped working

[devashish-sood]

Question

Despite no changes to the source code, my cron jobs stopped working today. Here are the contents of my vercel.json file:

{
  "crons": [
    {
      "path": "/api/choresEvening",
      "schedule": "0 1 * * *"
    }, 
    {
      "path": "/api/choresMorning", 
      "schedule":"0 14 * * *"
    }
  ]
}

I've set them up to execute serverless functions once a day, and I've confirmed that the functions are not erroring out by manually hitting them on the prod url.

[aal-khadzh]

I'm facing the same issue. Cron expression has been validated and job can be run manually by clicking "Run" button within Cron Jobs section of the project settings. When run manually, there is a log input appearing. However, logs doesn't show any API call around the time cron job is scheduled.

[justingebert]

Same here :/

[justingebert]

I'm facing the same issue. Cron expression has been validated and job can be run manually by clicking "Run" button within Cron Jobs section of the project settings. When run manually, there is a log input appearing. However, logs doesn't show any API call around the time cron job is scheduled.
@aal-khadzh
did you solve it? I am still having the issue. Could it be something with the execution limit?

[justingebert]

turns out it was a race condition in my case

[chreds]

I have the same issue but I'm not getting logs when the job is run manually from the cron jobs settings page although I can still run the job using postman and triggering it that way.

[chreds]

I found out what happened with mine. My nextjs file had a trailing slashes setting turned on so anything without a trailing slash was being forwarded. It looks like the cron setup in vercel will not follow redirects but doesn't log an error about it. So they were silently failing.

[teddis]

Thanks for the heads up. Happening to me and my trailingSlash was set to true. I am trying false. Can I assume this solved your problem? I'm also concerned with the lack of support monitoring and feedback here.

[chreds]

Yes, setting to false fixed it. Also you can try just adding a slash to the end of your cron job function path.

To be fair I emailed support and they were able to track this down for me.

[teddis]

Beautiful. Working now for me. I submitted ticket, and replied I got this working with your solution. I hope they update their documentation. Cheers.

[jasondainter]

Hero! Thanks this was driving me crazy, adding one trailing slash to my vercel.json fixed it!

Eg

"path": "/api/yourfunction**/**",

If you have

trailingSlash: true,

in your next.config.js

[jesper-bylund]

I'm also having the same issue. But it's clearly something that's happening, not a setting:
When I deploy a new version it works fine, then after a few days it stops triggering. No errors or reasons that I can find in the logs. 🤔

[muhammadkasimm]

In my case, I can't view my cron job under project Settings > Cron Jobs. My last deployment was about 300 days ago and I believe it was working fine until now, but now I can't even see it listed under Cron Jobs. Did they change something?

[github-actions[bot]]

This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community