# Does Twitter in node start repeating messages for anyone else?

**URL:** <https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337>\
**Category:** General\
**Created:** [9 January 2022 08:24 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337 "2022-01-09T08:24:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [9 January 2022 08:24 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/1 "2022-01-09T08:24:50Z")

</div>

I monitor cheerlights tweets using the twitter in node and every now and again - the debug node I have connected to it, starts displaying each message twice and keeps on doing it until I restart NR.

Its not a real issue for me as I just use it for info but I'm wondering if anyone else has noticed this happening to them.

---

<div class="post-metadata">

**Author:** ![andysc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andysc/32/21913_2.png) [@andysc](https://discourse.nodered.org/u/andysc)\
**Post date:** [13 January 2022 15:52 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/2 "2022-01-13T15:52:45Z")

</div>

I've noticed this after I do a partial deploy (flows only rather than full).  
Does this coincide with your observation, or do you see it after a period of running "untouched"?

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [13 January 2022 16:10 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/3 "2022-01-13T16:10:14Z")

</div>

I will test/watch out to see what happens

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [13 January 2022 17:59 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/4 "2022-01-13T17:59:54Z")

</div>

Perhaps the config node does not close properly, so you end up with two copies running.

---

<div class="post-metadata">

**Author:** ![andysc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andysc/32/21913_2.png) [@andysc](https://discourse.nodered.org/u/andysc)\
**Post date:** [13 January 2022 19:25 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/5 "2022-01-13T19:25:29Z")

</div>

that's my working theory 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [14 March 2022 19:26 UTC](https://discourse.nodered.org/t/does-twitter-in-node-start-repeating-messages-for-anyone-else/56337/6 "2022-03-14T19:26:22Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.