# Node Red Join when 3 MSG object come in
**URL:** https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099
**Category:** General
**Created:** [10 February 2022 20:01 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099 "2022-02-10T20:01:13Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@HarryPottar](https://discourse.nodered.org/u/HarryPottar)
#### Post date: [10 February 2022 20:01 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/1 "2022-02-10T20:01:13Z")
Hi,
I having a tuff time understanding the join node on a couple of flows I have.
One of my flows splits off to do 3 separate API calls. These 3 calls are inserting into 3 totally different system and each return an insert object id.
Split 1: msg.systemAInsertID =544466;
Split 2: msg.systemBInsertID =2333445;
Split 1: msg.systemCInsertID =112555;
I have a join that waits for 3 message parts and I think this is my issue.
I want to wait until all 3 messages are returned or 30 seconds time-out, combine all 3 message objects then continue that flow with just the single merged msg object.
I get all 3 messages back but my flows after the join runs 3 times. It runs the merged object 3 times. In other-words the object does have ALL 3 items but it runs 3 times.
Thanks In Advance
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2022 20:10 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/2 "2022-02-10T20:10:43Z")
Uncheck and every subsequent message. Then it should return one merged message every 3 incoming messages only.
---
### Author:  [@HarryPottar](https://discourse.nodered.org/u/HarryPottar)
#### Post date: [10 February 2022 20:16 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/3 "2022-02-10T20:16:58Z")
Thanks for quick feedback, I just tested that again and same issue, message is combined but the rest of the flow after the join still run 3 times.
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2022 20:19 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/4 "2022-02-10T20:19:42Z")
Then post your flow and the incoming 3 messages in 3 separate inject nodes . So we can see what is happening.
---
### Author:  [@HarryPottar](https://discourse.nodered.org/u/HarryPottar)
#### Post date: [10 February 2022 21:36 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/5 "2022-02-10T21:36:29Z")
I'm trying to set up a smaller workflow and simulate the issue.
The flow with this issue is huge and contains some propriety nodes that are security related and I can not share.
Thanks
Harry
---
### Author:  [@E1cid](https://discourse.nodered.org/u/E1cid)
#### Post date: [10 February 2022 21:41 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/6 "2022-02-10T21:41:32Z")
How many properties does each of the 3 incoming messages have each. As the merge option will count each property towards the join count.
---
### Author:  [@mickym2](https://discourse.nodered.org/u/mickym2)
#### Post date: [10 February 2022 21:41 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/7 "2022-02-10T21:41:37Z")
Security credentials will not be exported.
---
### Author:  [@HarryPottar](https://discourse.nodered.org/u/HarryPottar)
#### Post date: [10 February 2022 23:07 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/8 "2022-02-10T23:07:32Z")
This was the issue, number of msg properties.
On exiting the 3 flows before the merged I added a change node and delete all unnecessary properties.
Set the join to 12 and that worked.
Thanks Harry
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [24 February 2022 23:07 UTC](https://discourse.nodered.org/t/node-red-join-when-3-msg-object-come-in/58099/9 "2022-02-24T23:07:38Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.