If your n8n workflows run on a schedule, December is the month to act.
n8n 3.0 stable is due in early December 2026, and it drops the Cron node and the Interval node altogether. Every workflow that starts with either of them will show as Published after the upgrade — and never fire. No error, no failed run, nothing in the logs. The scheduler registers zero active triggers, because the node package no longer exists.
This is the quietest breaking change in 3.0, and it hits the most workflows.
What replaces Cron
The replacement is the Schedule Trigger node. Your cron expressions move into it, and it respects GENERIC_TIMEZONE or the per-workflow timezone setting. Interval schedules become a Schedule Trigger set to run every X minutes, hours, or days.
That is a small change per workflow. The work is finding every workflow that uses Cron or Interval before you upgrade, because the dashboard will not tell you — they all still look active.
Building the times
A Schedule Trigger still needs a schedule. If you are rebuilding a dozen cron expressions by hand, a generator is faster than guessing the syntax.
I built a free one: https://fasttools.me/crontab-generator
Pick the minute, hour, day, month and weekday, and it gives you the expression — no account, no tracking, nothing runs on a server. Use it to build the times, then paste them into your Schedule Triggers.
One tip from the migration: check the timezone on each workflow while you are in there. A schedule that ran at 9am under Cron will run at 9am under the Schedule Trigger only if the timezone matches. The trigger respects the workflow timezone, so a mismatch moves the run silently — same failure shape, different cause.
The wider 3.0 picture
Cron and Interval are two of 37 nodes removed in 3.0. The others include the Function and Function Item nodes (replaced by the Code node), Item Lists (split into single-purpose nodes), the legacy OpenAI node, and the old AI Agent modes. The full list, with every replacement and the upgrade runbook, is in the SOP I wrote: https://whoisalfaz.me/blog/how-to-upgrade-to-n8n-3-without-breaking-workflows/
Three things from that guide worth knowing before you touch anything:
- The upgrade is one-way. No rollback to 2.x except restoring a full backup.
- npm and npx installs are gone. Self-hosted n8n runs on Docker only from 3.0.
- Your error handler will not catch a trigger dropout. If no execution ever starts, the Error Trigger never fires — so a workflow can be dead for days before anyone notices.
Build your new schedules now, while the beta is still out. December is close, and the workflows that look fine are the ones to check first.
Alfaz Mahmud Rizve — GTM & RevOps Architect. I build autonomous revenue systems for scaling agencies and SaaS: SEO & organic growth, high-speed Next.js apps, and self-healing n8n workflows. whoisalfaz.me
Top comments (0)