Issue Station
Sign In
Tools hereToolbox

n8n - ✅(Solved) Fix Duplicating tabs in chrome causes websocket network disconnection [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • error: all

PR fix notes

PR #28764: fix(editor): ensure duplicated tabs use unique push refs

Description (problem / solution / changelog)

Summary

<!-- Describe what the PR does and how to test. Photos and videos are recommended. -->

before:

https://github.com/user-attachments/assets/72a247e5-31b6-4c46-9dec-51e6adcc951a

after:

https://github.com/user-attachments/assets/47c224d7-9b46-4a8e-b90d-8eb3eed8c6f8

Related Linear tickets, Github issues, and Community forum posts

<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/[TICKET-ID] --> fixes #28741

The problem :

duplicating a tab also duplicated the session storage and hence the same pushRef.

The fix:

  1. If found a duplicate pushRef,a new client id is generated and replaced in session storage so the collision doesn't happen.
  2. Used BroadcastChannel to check for duplicate pushRef's across different tabs from same origin.
<!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->

Review / Merge checklist

  • I have seen this code, I have run this code, and I take responsibility for this code.
  • PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
  • Docs updated or follow-up ticket created.
  • Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)

Changed files

  • packages/frontend/@n8n/stores/src/useRootStore.ts (modified, +122/-6)
  • packages/frontend/editor-ui/src/app/stores/pushConnection.store.test.ts (modified, +13/-3)
  • packages/frontend/editor-ui/src/app/stores/pushConnection.store.ts (modified, +11/-1)

Code Example

(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.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

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

<!-- If you need help with data transformations, please also share your expected output. -->

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

extent analysis

TL;DR

The issue can be mitigated by ensuring that each n8n tab in Chrome has a unique state to prevent conflicts in network connections.

Guidance

  • Investigate how the state is being copied over when duplicating n8n tabs and find a way to generate a unique state for each tab.
  • Verify that the WebSocket connection is being established correctly for each tab by checking the browser's developer tools for any error messages.
  • Consider using a different method to duplicate the workflow, such as using the n8n UI to create a new workflow and then copying the nodes over, to avoid copying the state.
  • Check the n8n documentation for any known issues or limitations related to duplicating workflows and WebSocket connections.

Notes

The exact cause of the issue is unclear, but it appears to be related to the state being copied over when duplicating n8n tabs. Further investigation is needed to determine the root cause and find a permanent solution.

Recommendation

Apply a workaround by ensuring each n8n tab has a unique state to prevent conflicts in network connections, as this is the most likely cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#mixed precision#training loop#device allocation#model download

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - ✅(Solved) Fix Duplicating tabs in chrome causes websocket network disconnection [1 pull requests]