Duplicating tabs in chrome causes websocket network disconnection

[Undre4m]

Describe the problem/error/question

When duplicating n8n tabs in Chrome browser the copied over state causes both network connections to fail.
Chrome Version 147.0.7727.56 (Official Build) (arm64)

What is the error message (if any)?

installHook.js:1 [WebSocketClient] Connection lost, code=1005
overrideMethod @ installHook.js:1

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

N/A

Share the output returned by the last node

N/A

Debug info

core

• n8nVersion: 2.16.1
• platform: docker (cloud)
• nodeJsVersion: 24.14.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 200
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-04-20T18:36:35.618Z

[glenbenatiro]

Same issue here #28281

[aakash2330]

I did some research and here's what's happening -

1. duplicating a tab also duplicates the session storage.
2. it means both have the same pushRef. Hence the connection lost error ( server removes duplicates )

[aakash2330]

here's how my approach to fix it would be

1. I'll use BroadcastChannel to check for duplicate pushRef's across different tabs from same origin.
2. If found a duplicate, I'll just generate a new client Id and replace it on the newly created/duplicate tab.

@ivov

[n8n-assistant]

Hey @Undre4m,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7791".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7791