Unverified50% confidenceReleaseExact time
The behavior change introduced in n8n 2.43.7 is: when a Worker shuts down, the system pauses in-progress production runs rather than losing them.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
New n8n Release: Worker Restarts No Longer Lose Running Workflows
youtubeAI INCOME TIP10/17/2026
Related Entities
Related Claims
UnverifiedThe update fixes the issue where canceling immediately after sending a message now truly stops the task; previously, a cancellation occurring during the turn initialization phase would be ignored and the task would continue running.65% similarUnverifiedThe crash test is performed by killing the n8n execution midway and then rerunning with the same transcript, asserting: no duplicate action items (idempotency is achieved by performing an upsert on meeting ID + item hash), items already extracted before the crash are not extracted again, and the run log shows a retry rather than a silent overwrite.63% similarUnverifiedv3.0.71 fixed three issues with scheduled runs: queued runs no longer remain permanently in the pending state; runs whose model calls fail are marked as failed with the error message attached; and after recovering from a service outage, only the most recent missed time point is executed, rather than catching up on all missed runs.62% similarUnverifiedAfter modifying the timezone in the workflow Settings, you need to save and re-run the workflow for it to take effect.62% similarUnverifiedn8n automatically retries upon enabling failure retry when an AI provider is overloaded, whereas a Zapier run stops entirely and must be manually replayed from the history.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1059381API
curl https://kongchang.com/api/v1/knowledge/claims/1059381MCP
get_claim(id=1059381)