n8n's new default survives restarts but drifts off the clockn8n 的新默认重启不丢任务，却也不再对齐整点

Your "every 15 minutes" jobs may fire at new times after you upgrade.

And the opt-out is already deprecated

OUR READ

Durable scheduling is a real reliability win. But it's a trade, not a free upgrade — and the choice was made for you, by default.

WHAT HAPPENED

• n8n 2.45 (Oct 20) turns the durable scheduler on by default for every instance.
• Scheduled runs now persist to the database before they're due, so a restart no longer drops pending runs.
• But "every N seconds/minutes" now runs at a steady interval measured from when you published the workflow — no longer aligned to clock boundaries.
• The clock-aligned legacy mode and the old in-memory scheduler both now emit deprecation warnings; the Skip Durable Scheduler setting was removed.

WHY IT MATTERS

For most solo self-hosters the rare win is "a run survived a restart." The silent cost is any job that assumed clock-aligned timing — API rate windows, hand-offs between workflows, reporting cutoffs.

A default that survives restarts but drifts off the clock is a trade, not a free upgrade.

Second-order: the opt-out is deprecated on arrival, so reverting only buys a few months — the real cost is a forced redesign before 3.x removes the bridge.

BEST CASE AGAINST US

Hourly, daily, weekly and cron triggers are unchanged, so anything that truly needs clock alignment can move there. For pure polling jobs, drifting off the clock means nothing.

DO THIS WEEK

If you self-host n8n: list your scheduled workflows, mark the ones that depend on clock alignment, and move those to cron triggers now — don't lean on the deprecated legacy flag.

We change our mind if n8n keeps a supported clock-aligned interval option in 3.x, or shows cron triggers already cover every alignment case.