Hello and good day, having this issue explained below would appreciate any help or insight, thank you
Existing /api/discover-worker job runs correctly, but new cron jobs (/api/vetting-worker, /api/job-completer) are not triggered despite multiple successful deployments with updated vercel.json.
The existing /api/discover-worker job runs correctly with vercel-cron/1.0 User-Agent
Multiple successful deployments with updated vercel.json have not updated the cron job registry
New cron jobs (/api/vetting-worker, /api/job-completer) are never triggered
Already verified vercel.json syntax is correct
Confirmed cron expressions are valid (* * * * *)
Tested with simplified configuration (single cron job)
Multiple deployments with different configurations
All deployments show “Ready” status
Only the original cron job is registered and displayed, despite vercel.json containing multiple valid cron job definitions.
current vercel.json configuration:
{
“crons”: [
{
“path”: “/api/discover-worker”,
“schedule”: “* * * * ”
},
{
“path”: “/api/vetting-worker”,
“schedule”: “ * * * ”
},
{
“path”: “/api/job-completer”,
“schedule”: “ * * * *”
}
]
}