Unknown node - Flow does not start

Hi,
I copied some flows from a friend to extract some functionalities.
Unfortunately there are some unknown nodes included and Node-Red refuses to start.

I would love to have these copied flows being ignored by Node-Red - I just want to peek from time to time.
Is there a way to do this?

I tried to delete the unknown nodes in the Konfiguration node, but unfortunately I seem not to find all unknown nodes. Deactivating the nodes does not help here.

My last idea is to set up a second server, but there has to be an easier way...

Kevin

Welcome to the forum @KevinT

Once you have deleted all the unknown nodes in the flow there may be configuration nodes in the import. To find those look in the Menu for Configuration Nodes. Click Unused at the top of the list and it will show you if there are any of those. You can select and delete them.

I think that if you disable the flows containing the unknown nodes that that might allow it to run, but I am not certain. Again configuration nodes might be an issue. If you double click the flow tab then there is an Enabled status down the bottom that you can click to disable it.

Why don't you just install the nodes?

@Colin
thanks for the answer.
Certainly ther are some unused nodes, but how do I identify the broken (or non-existing) ones?

Actually there are several flows and subflows. As I was not able to disable a subflows I just deleted all unknown nodes from all flows. That seems not to be sufficient / some nodes seem to be hiding...

Why not install the missing nodes?

  1. I do not need them. That flow comes from a bigger system with a lot of different databases, user handling and multi-server support. I just want to copy some functionalities of the full system.
  2. I do not know which are the missing ones. On deploy I get a warning about missing nodes (e.g. excel), but I do not find the nodes - neither in the node list, nor in the configuration nodes.

I believe they show up as unknown type. Though you can delete any unused config nodes, unless there is a reason you want to keep them around. They are just using up resources to no good purpose.

There are no unknown configuration nodes. And there are no unknown node in Any Flow. But still: Node red alerts some missing nodes on deploy and rejects Starting (After deploy)

What missing node types is it complaining about?

Don’t have them in front of me now, but it was an e-Mail node and an crypt node (qcrypt ?)

Please stop node red and then start it again in a terminal and post the full terminal output here.

Depending on how you installed node-red you may be able to do that using
node-red-stop
node-red-start

When you paste it use the </> button at the top of the forum text entry window, which will stop the forum from messing with the format.

I managed to find the remaining unknown nodes.

I used the search field in the info tab of node red and found the unknown nodes. After deleting them node red works perfect.

Thanks Colin for your support !

Out of interest, why did you not see them before?

For future reference, you can search for type:unknown

chrome_5JJjc7RQdf

1 Like

I did not search the flows in the info tab, but in the workspace. I did not find the nodes there.
They were not in the conficuration tab either.

When you did find them, where were they?

They were in one of the inserted flows. I searched them thoroughly (in the workspace) and they did not show up there.
So it seems they were not in use but still in the list... ? Or hidden behind a known node?

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