I have this subroutine which I am calling with a link call node: [Screenshot 2024-01-04 alle 16.10.24] I am always getting "Missing return node information", due to the split function, which contains: msg.payload.split("##").forEach(e => { if (!e) {return;} node.send({ payload: e + "##"…

Try this then. you will need to remove the "fake data" node and check that the output of the EXEC maintains the msg.linksource property for it to work in production. [{"id":"f4fddf75fcab76bd","type":"inject","z":"eaa6d97a6ede80ab","name":"*#*1##*#*1##*#18*5158*113*490##*#*1##","props":[{"p":"data"…

fmarzocca 4 January 2024 16:12 21

Thank you very much for your patience and sorry for the long thread!

Topic		Replies	Views
Option in "Link-Call" to discard response after timeout Feature Requests	11	651	23 January 2023
Clarifying use of split node General	17	578	10 April 2021
Split node to output complete:true when finished Feature Requests split	22	212	10 March 2025
Split-Node an using only couple payloads General split	7	572	25 May 2022
Allow input other than msg.payload for the split node Feature Requests	11	1086	29 January 2022

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.

Subroutine Missing return node information

Related topics