Need a bit of help In this example - I'm splitting a msg and doing stuff in a parallel and then I want to recombine. [image] [image] [{"id":"f14cd0c.f486c3","type":"inject","z":"29e0a8a9.d58188","name":"","topic":"","payload":"3","payloadType":"num","repeat":"","crontab":"","once":false,"onceDe…

[image] cymplecy: I actually want the output msg. to be Brain has re-engaged :slight_smile: Just need a change node to move things around [image] [image]

It would have to be a hell of a lot more complex a set of calculations to make it worth the complexity of trying to do parallel processing. Just do it in a single change node.

The real world problem is a hell of a lot more complex :slight_smile: (Its adding an image file to a tweet - the processing destroys msg.payload so hence need for sidechain)

Why not move msg.payload to msg.orig_payload and keep it in the msg object?

If you really need to do parallel processing, either start with a split node or add the msg.parts object to the msg on each parallel leg of the flow, so you can use a join node (set to 'Automatic' mode) at the end of the flow. But in general, if each leg is a synchronous task, they will have to be …

[image] zenofmud: Why not move msg.payload to msg.orig_payload and keep it in the msg object? [image] shrickus: If you can include some actual input data, and a sample of what you need at the end, it would make a nice little "contest" for the community to come up with different solutions.…

Relying on msgs arriving at the right times is almost never the best solution. And with the new asynch flow processing in v1.0 it may not even work the way you expect.

[image] shrickus: Relying on msgs arriving at the right times is almost never the best solution. That's why I wanted to try a different approach :slight_smile: I used flow context and timing when I was a newbie :slight_smile:

You might try this though I don't know whether it will actually give you better performance: [image] node-red-contrib-actionflows Create extendable, loopable, and reusable design patterns for flows.

This discussion highlights a bit of a missing piece of core functionality: how to "fan out" 1 msg into N identical msg objects with the msg.parts set correctly, so a join in "automatic" mode will do the right thing... In the past I've used a function node, cloned the incoming msg objects, added the…

[image] TotallyInformation: You might try this though Its nice looking way of effectively having callable functions but have to do the msg.payload_orig method so each function get msg.payload as its input [image]

Node-RED

Node-RED Forum

Split- process separately - recombine

General

TotallyInformation 16 September 2019 15:16 10

You might try this though I don't know whether it will actually give you better performance:

Topic		Replies	Views
Issue joining parallel flows into one General	6	336	17 August 2022
Split messages arriving out of order General	29	448	19 December 2022
Split should send complete message once all has been split General split	28	134	17 January 2026
Split node to output complete:true when finished Feature Requests split	22	202	10 March 2025
Does "split" node clone messages? General	14	807	3 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.

Split- process separately - recombine

Related topics