Node-Red 5.0.0 import on current flow (tab) broken

General
1

Not a huge issue and an acceptable workaround.
When importing a flow, selecting Import on the Current Flow tab always creates a new tab.

A simple copy-and-paste fixes it, but it's worth noting. Tested on macOS Tahoe 26.5.1 and Chrome Version 149.0.7827.197

2

From where are you importing the tab?
Same machine? :man_shrugging:

How are you exporting the code?

export with nodes selected or do you select tab after selecting export?

Also, if you exported a tab and import to current tab: it may be problematic.
(Had to think how to put that a few times as all I could ge twas local talk and that wouldn't translate too well.)

3

I'm running version 4.1.7, going into the menu, and exporting the flow.
I have tested both exporting to file and copying JSON to the clipboard.

I'm exporting selected nodes, not entire tab.

Then, in 5.0.0, I go to the menu and select Import, then I select where to import to: current flow, yet it always create a new flow (tab)

Screenshot 2026-06-29 at 10.41.57 PM
Screenshot 2026-06-29 at 10.41.57 PM1400Ă—1186 52.6 KB

4

Ok.

Sorry, beyond my skill set.

5

Could you post a small example flow that will not import into current tab please.

6

I've also seen this effect from time-to-time.
Just tried Export/Import flows on NR version 3.1.11 and 4.1.11 and can't reproduce the effect.

7

I think it depends how you exported. If you export "some" nodes then you can import to current flow, but if you export the complete flow (tab) it creates that same tab when you import.

8

I've also seen this very often in previous releases.