n8n 2.35.5 Highlights Why Slow Task Runners Should Not Be Auto-Restarted
The release notes for n8n version 2.35.5 include a notable operational insight: a slow task runner should not be treated as a dead one. Many workflow systems mistakenly combine task duration with liveness, causing supervisors to restart workers that are still making progress, which can duplicate tool calls or trigger retry storms. A more robust approach involves checking heartbeats, progress markers, and external dependencies before deciding to restart. The release also notes that the expression engine now initializes only when needed and test webhooks are released after teardown, reflecting a broader principle of avoiding unnecessary state or work. Taken together, the changes emphasize precise, context-aware recovery over blunt timeout-based restarts.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in