n8n | n8n@2.32.6

n8n n8n@2.32.6 released on 29-07-2026


n8n n8n@2.32.6 is out now. It fixes schedule trigger parsing so common 5-field cron expressions (minute hour day month weekday, for example “0 8 * * *”) are accepted, preventing failures or rejections when those crons are supplied.

See the GitHub compare for 2.32.5…2.32.6, issue #35013 and commit 0de32f0 for the full details; upgrade the package or container and restart n8n instances to pick up the fix.

What’s in this release

  • Schedule trigger parsing updated to accept 5-field cron expressions (e.g. “0 8 * * *”).
  • Bug tracked as issue #35013 addressed.
  • Change implemented in commit 0de32f0 and published as n8n@2.32.6.

Upgrade notes

  • No breaking changes; workflows using Schedule Trigger with 5-field cron syntax require no changes and remain compatible.
  • To apply the fix update to 2.32.6 (package or container) and restart n8n instances; no database migrations or configuration changes are required — monitor scheduler logs for expected behaviour.

Share comments on your experience after upgrading, especially if you relied on 5-field cron schedules in production.

Related posts

Weekly Tech Digest | 12 Oct 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

Removed SSRF beta detections in Cloudflare WAF

Cloudflare WAF Managed Rules have a habit of changing underneath you, and old SSRF names can linger long after the protection has gone. I prefer to check the live block logs, then test the ugly...

Weekly Tech Digest | 28 Sep 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.