# Tcp in node loosing/stacking messages

**URL:** <https://discourse.nodered.org/t/tcp-in-node-loosing-stacking-messages/15049>\
**Category:** General\
**Created:** [3 September 2019 09:29 UTC](https://discourse.nodered.org/t/tcp-in-node-loosing-stacking-messages/15049 "2019-09-03T09:29:15Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [4 September 2019 21:04 UTC](https://discourse.nodered.org/t/tcp-in-node-loosing-stacking-messages/15049/12 "2019-09-04T21:04:20Z")

</div>

> [@SeRiusRod](#):
>
> Ok, I think I've got it under control.

Glad to hear you've solved the problem. For the record, I think I had a similar issue with data coming in through the `exec` node. I was able to fix it using an [optional configuration](https://discourse.nodered.org/t/exec-and-daemon-nodes-break-up-a-data-stream/10695/20) of the `split` node. You might give it a try.

---

_[View the full topic](https://discourse.nodered.org/t/tcp-in-node-loosing-stacking-messages/15049)._