Nothing specific to queue mode. Since each worker needs its own runner, you need to configure separate ports for each worker so they don’t overlap. See docs here.
Hello,
For the new sub-workflows feature, does it mean that we can add Respond to chat node in the child workflow while the Chat trigger node is in the parent and it will work? and what about webhook trigger and respond to webhook?
Hi @mbn8n
No that is not possible, and I don’t think it ever will, as the executions are fully isolated from each others (they can’t access nodes from each others).
Hi! Do you know when the n8n v2 Docker image will be pushed to the latest tag?
6 Likes
version 2.1.0 (2025-12-15) is now in beta…
is it becoming the current version today?
2 Likes
Overall 2.0 looks great with the new UI changes but come on what is this:??
This change is backwards - small icons, color contrast is low, icons are tiny, it’s barely distinguishable between which workflow is published or not published.
Can we not have the toggle back as that was an instant obvious visual cue as to the status - this I have to really look and zoom in when I have n8n displayed on my 32” monitor.
2 Likes
My system updated to V2 over night during its maintenance cycle. Everything is looking great. All workflows working with no errors, n8n logs are clean. I’m grateful for the V2 migration report, it really helped me to prepare for the update.
2 Likes
Exciting News for the Automation Community!
I’m genuinely excited about the upcoming release of n8n v2.0.0 — a major milestone that reflects how far the platform has evolved since its 1.0 launch in 2023.
1 Like