# Problem detected when migrating subflows between machines

**URL:** <https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495>\
**Category:** General\
**Created:** [8 June 2025 22:16 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495 "2025-06-08T22:16:28Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 10:21 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/21 "2025-06-09T10:21:07Z")

</div>

Error after reconnecting the input wire and deploy.

 ![Screenshot from 2025-06-09 20-15-01](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/8/08145271787cbafb0118842f4c9df2c034e8614e.png)

Switched to FULL DEPLOY

 ![Screenshot from 2025-06-09 20-17-29](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/b/ab41e172268fd1ecc3cda4b6d21f156ab679fd8e.png)

Working.

Go figure.

So should I COMPLETE/SOLVE mark this or leave it open so people in the know may look at it and maybe dig into what happened as there should be better error notification happening.  
and the weird fact that I could have two of the same subflow and one makes errors and the second one doesn't.

🤷

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [9 June 2025 10:24 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/22 "2025-06-09T10:24:37Z")

</div>

This is a bug. Can you give us a minimalist flow to reproduce the problem?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 10:26 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/23 "2025-06-09T10:26:16Z")

</div>

No.  
(not being rude. just stating the fact)

What ever the problem is/was has now been fixed when I did the full deploy.

Which is not a good reflection on me for not thinking of doing that.  
But....

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 22:24 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/24 "2025-06-09T22:24:22Z")

</div>

# GOOD NEWS / BAD NEWS!

Today I was cleaning up flows. Moving nodes, all that stuff.

The problem is back.

But HOW it was caused.... Dunno.

## TO RECAP

It would SEEM that if I (only/simply/even) move a `subflow` and re-deploy (modified nodes only) the problem can reoccur.

The **BIG PROBLEM** is there is NOTHING in the messages to identify WHICH ONE.

## P.S.

Yesterday doing a FULL DEPLOY fixed the problem.  
Though admittedly that was AFTER I found which `subflow` was causing the problem.....  
FULL DEPLOY hasn't worked this time.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 22:48 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/25 "2025-06-09T22:48:13Z")

</div>

# SUPER URGENT UPDATE!

# FOR DEVELOPERS TO READ

Ok, so the story so far:

I am/was/am getting these weird messages of an error with NO identifiable node.  
Hinting at a SUBFLOW. _(important)_

All reports are now for ONE machine.

I got lucky yesterday and discovered it was my `MachineHealth V2` subflow.

If it was DISABLED but wires left going INTO it: I got the errors. _(Note)_  
ONLY if I removed the wires did the errors stop!! 🤨

I _exported_ the nodes and put them on the flow level. They worked.

If I put a SECOND COPY of the `subflow` and tested it: **IT WORKED!!**

Clutching at straws, I put a THIRD copy (left the initial copy else where on the flow) and switched the ORIGINAL one with the THIRD COPY.  
Wired it up.  
It worked. No errors.

NR 4.0.9.  
Node.js 18.20.8  
Buster.

So today while tidying up **ANOTHER** flow on this machine I started getting these errors.

Checked all the `subflows` I'd moved. NOTHING.

Then - again: on a whim and prayer - I unwired the `MachineHealth V2` subflow.

## FIXED!

Dragged another one from the left and put it in.  
Wired it up.  
Deleted the original one.  
DEPLOYED.

NO ERRORS.

Sorry, I forget if it was modified nodes or full.  
But I suspect modified nodes.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 22:52 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/26 "2025-06-09T22:52:36Z")

</div>

# AND ANOTHER UPDATE!

(I'm stupid.)

I didn't actually check the subflow. I put it in, the errors stopped.

But....

The subflow is _EMPTY_!

 ![Screenshot from 2025-06-10 08-51-55](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/e/8e18223eddb05c849421f0d04925fb0319fc4ff6.png)

So - of course - there won't be any errors.

It is not doing anything.

# H E L P !

This is what it is supposed to look like - after another export/import from another machine.

 ![Screenshot from 2025-06-10 08-54-51](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/8/08cecb6b02f8d865f0bcfd3ec45d05618658fd6c.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 September 2025 22:53 UTC](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495/27 "2025-09-07T22:53:25Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/problem-detected-when-migrating-subflows-between-machines/97495.md?page=1)