Yes, how I am doing it may be making my own life miserable, but it's the only way I know. Details - as best I can give: EXPORTING FROM: NR 4.0.9 IMPORTING TO: NR 3.0.2 and 4.0.9 I would import it, REPLACE the node, and do a bit of fixing up of other stuff. ALSO: The subflow had been severely…

Third/fourth? time lucky. All the wires are now there on THAT subflow. Still getting the rogue messages. (Don't know if they should be a separate thread) I quickly checked a couple of other subflows on that tab.... All seem ok. I'll do a bit more comparing now.

Ok, I have copied the Offending files to my machine. They are all .json files. [Screenshot from 2025-06-09 11-26-21] And dated recent. I opened a new tab and tried to import the Flow.js. Wouldn't. [Screenshot from 2025-06-09 11-30-29] Anyone recognise this code? (Incomplete. Too long to p…

This is group.js (Short) const flowUtil = require("./util"); const credentials = require("../nodes/credentials"); const clone = require("clone"); /** * This class represents a group within the runtime. */ class Group { /** * Create a Group object. * @param {[type]} parent The…

I had a similar issue a while back , when moving code (incl subflows) from my dev machine to my prod. I check the code on a WIN and MAC machine and the lines were missing in both systems A full shutdown of my PROD system solved the issue.

I'm not sure I understand what you did to fix it.

ANOTHER DEVELOPMENT So thing are really getting bad here. I explained how I imported the subflow; all the wires aren't getting there. After several attempts it was all working. Yeah, nice. BUT! The machine started to get these rogue messages. Out of desperation, I updated it to the lates NR. 4…

AND ANOTHER IMPORTANT UPDATE ON WHAT'S HAPPENING Well, this is a weird one. The subflow was DISABLED. All the wires into/out of it were rerouted to the exported nodes that were sitting at the same level/layer as the others. Note: It was DISABLED. I left the wires going in/out of it. (This is im…

My system is running on docker, so I completely restarted the NR docker ... full system restart for Node-Red

I am stupid. I am not understanding what you mean. What? You simply go into the CLI/Terminal and node-red-restart?

Node-RED

Node-RED Forum

Problem detected when migrating subflows between machines

General

Trying_to_learn 9 June 2025 01:51 12

I notice a very similar problem happened a long time ago:

Something similar

Topic		Replies	Views
Link-out link-in in subflows, after copy General	31	604	7 June 2024
Imported subflow does not work General	4	471	18 December 2020
Subflows stopped working suddenly General	6	1453	30 May 2019
Throwing errors - help please General	30	668	11 February 2024
Subflow input output wires disappear Core Development	28	2073	10 July 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Problem detected when migrating subflows between machines

Related topics