Scheduled functions silently not firing automatically (manual triggers work)

[Haydsamp26]

My scheduled functions show the Scheduled badge and correct next-execution timestamps in the dashboard, but they are not actually firing on schedule. Manual triggers via “Run now” and via authenticated POST requests both work perfectly — the function code itself is fine. The problem is purely scheduler-side.

Affected functions:

• monthly-reminders — schedule 0 9 1 * *

• daily-expiration-alerts — schedule 0 8 * * *

• bonus-alert — schedule 0 9 * * *

• sync-transfer-bonuses — schedule */15 * * * *

• welcome-email — schedule */15 * * * * (deployed today)

• validate-sheet — scheduled

Evidence:

monthly-reminders is scheduled for the 1st of each month at 09:00 UTC. The function log (7-day retention per the dashboard banner) contains zero invocations on May 1, 2026 at 09:00 UTC. The most recent entries are from April 27 when I manually triggered the function via authenticated curl during a debugging session — visible because they’re within the 7-day window.

If the scheduler had fired on May 1 at 09:00 UTC, that invocation would still be within retention and visible in the log. It is not. I had to manually trigger the May 1 monthly run when I noticed users hadn’t received emails.

This matches the symptom pattern in this April 12, 2026 thread which support resolved within ~24 hours: https://answers.netlify.com/t/scheduled-functions-silently-stopped-being-invoked-no-errors-no-logs/161356

What I’ve already verified:

• All affected functions show the Scheduled badge in the Functions tab

• All show legitimate “Next execution” timestamps

• Manual “Run now” from the dashboard works

• Authenticated POST triggers (with a CRON_SECRET header) work and complete successfully end-to-end

• Code, env vars, Supabase, and Resend integrations are all healthy

• Schedule annotations in source files (export const config = { schedule: ... }) match netlify.toml entries

• No DNS or build issues; latest deploy succeeded

  

Context (in case it helps prioritize):

This is a production app with paying users. I have a public launch planned for tomorrow morning (May 4) that depends on the welcome-email cron firing on schedule for new signups. Will be filing a backup external cron in the meantime, but a real fix on the Netlify side is what I’m hoping for.

Happy to provide additional diagnostic info, function logs, or screenshots — let me know what’s useful.

Anyone else seeing this on their site today? Trying to gauge whether this is account-specific or platform-wide.

Thanks, Hayden

[statusbot]

Hey @Haydsamp26 ,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!