Subflows broken with 0.20.0

#1

Hi, I have tested this with a simple "hello world" function.

image

The datamapper is a hello world for now:
image

the function "hello":
msg.payload = "hello world";
return msg;

When I hit the inject node, I see nothing in the debug console. This works fine in previous versions.

Thanks,

Carlos Marin

0 Likes

#2

Works fine for me - please provide your exact flow.

0 Likes

#3

I'm working on Bluemix NodeRED. I will create another instance and test again and if it doesn't work, I'll paste the complete flow here. Thanks.

0 Likes

#4

I just reproduced it on a clean 0.20.2 build. How do I upload attachment? It says I'm a new user so I can't upload the flow.

0 Likes

#5

Paste flow here:

[{"id":"b380f145.2a52","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"a7f6f640.5d3568","type":"subflow","name":"hello","info":"","category":"","in":[{"x":120,"y":100,"wires":[{"id":"97471d17.7e59a"}]}],"out":[{"x":380,"y":100,"wires":[{"id":"97471d17.7e59a","port":0}]}],"env":[]},{"id":"97471d17.7e59a","type":"function","z":"a7f6f640.5d3568","name":"hello","func":"msg.payload = \"hello world\";\nreturn msg;","outputs":1,"noerr":0,"x":250,"y":100,"wires":[[]]},{"id":"f14482d0.20d77","type":"inject","z":"b380f145.2a52","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":140,"y":140,"wires":[["53354d28.fa51a4"]]},{"id":"53354d28.fa51a4","type":"subflow:a7f6f640.5d3568","z":"b380f145.2a52","name":"","x":320,"y":140,"wires":[["d0db4ce5.84c91"]]},{"id":"d0db4ce5.84c91","type":"debug","z":"b380f145.2a52","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":500,"y":140,"wires":[ ]}]
0 Likes

#6

Hi @caralmar
the flow you've shared works fine for me.

In the same Node-RED instance, could you add a simple Inject->Debug flow and check you get those messages in the sidebar?

It could be an issue with the websocket comms connection between the editor and runtime stopping the messages from appearing - giving it the impression that the flow isn't working.

0 Likes

#7

Hi, I can give you access to that env. It is running in IBM Cloud. Empty env. Just the one flow. This problem first manifested itself when I was turning a mapping function into a subflow so I could use it in some other flows. The mapper is invoked via a REST API. When I invoke it using POSTMan, it just hangs, waiting on a response. It is then that I discovered that the subflow is not responding. If you would like to see it first-hand, please ping me on Slack (cmarin@us.ibm.com). Thanks.

Carlos.

0 Likes

#8

For anyone reading along at home, the problem has been identified to the fact the instance was using Node 6.x - not the required 8.x or later.

We're working on getting the IBM Cloud boilerplate for Node-RED updated to pull in Node 8.

2 Likes

#9

Thanks for your help. I manually upgraded that instance to NodeJS 8.x and can confirm that the subflow is working now.

Take care,

Carlos.

0 Likes