n8n 2.43.4 - Queue Mode Chat Hub Fix and Deferred Tool Resume

n8n published [email protected] on October 12, 2026. It is a patch release with exactly two fixes, both in core. The one that matters most to operators is a queue mode correction that ensures each Chat Hub segment is handled once instead of more than once.

The full release notes and downloads are on the GitHub release page. This is not a prerelease. There are no breaking changes and no migration steps in the notes.

The first fix, #40816 (commit dc77062), changes how the core processes Chat Hub segments when the instance runs in queue mode.

Queue mode splits work between the main process and worker processes, with jobs handed over through a message queue. In that topology, a segment ending up in more than one consumer is a real operational problem: duplicated segments mean duplicated side effects downstream, and Chat Hub conversations are stateful, so replaying a segment can desynchronize the conversation state from what the user actually saw.

The fix limits handling to one pass per segment. If you run Chat Hub workloads on a queue mode deployment, this is the release to pick up. Single process mode was not the reported failure surface here, so the fix is most relevant if you scale workers horizontally or have retries configured that could redeliver jobs.

The second fix, #40746 (commit ea448c6), covers tool call resumption for deferred tools that a skill loaded. Deferred tools are invoked asynchronously; the workflow pauses on the tool call and resumes when a result comes back. The bug was that a tool registered by a skill, rather than defined directly on the workflow, did not resume correctly from its deferred state.

For anyone building agentic flows where skills register tool sets dynamically, this closes a path where a run would stall or drop the tool result. It is a correctness fix in the execution model, not a feature change. No configuration keys change.

That is the whole release. Two fixes, both tagged core in the notes. No dependency bumps, no CVE fixes, no editor or UI changes called out. If you are running [email protected] and you do not use Chat Hub in queue mode and do not use skills that load deferred tools, there is little in this release for you, and skipping it is a defensible choice. If you do run either pattern in production, the duplication and stall risk is worth the upgrade.

The project also carries auto generated review links from cubic in the release description. Those are tooling artifacts from the release pipeline, not part of the changelog, and there is nothing operator visible in them.