# Messages blocked till next deploy

**URL:** <https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237>\
**Category:** General\
**Tags:** node-red-contrib-lgtv\
**Created:** [24 January 2026 14:12 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237 "2026-01-24T14:12:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gnomi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gnomi/32/67756_2.png) [@Gnomi](https://discourse.nodered.org/u/Gnomi)\
**Post date:** [24 January 2026 14:12 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237/1 "2026-01-24T14:12:36Z")

</div>

I sometimes have the feeling of blocked messages inside Node-Red (currently 4.0.5).  
Then some functions -not all- are not working anymore and if I make a full deploy of the flows again, all is working and in e.g. using node-red-contrib-lgtv the messages towards a LG-TV all blocked messages are coming afterwards.  
Sorry to be not more detailed. But is this a known Node-Red issue or where can I search for the possible reason of this behavior?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [24 January 2026 14:23 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237/2 "2026-01-24T14:23:14Z")

</div>

That sounds like you could have a backlog of messages waiting to be processed.  
The full deploy would clear out the queue.  
Have you checked for runaway loops, including MQTT in and out nodes using the same topic?

---

<div class="post-metadata">

**Author:** ![Gnomi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gnomi/32/67756_2.png) [@Gnomi](https://discourse.nodered.org/u/Gnomi)\
**Post date:** [8 February 2026 15:08 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237/3 "2026-02-08T15:08:17Z")

</div>

Thank you @jbudd. I checked also the MQTT side but could not find any loop. So still not clear what causes this issue. I am thinking about adding a MQTT monitoring with Gafana presentation to see any message peaks on this side.

---

<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:** [8 February 2026 15:38 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237/4 "2026-02-08T15:38:55Z")

</div>

Check the CPU usage on the machine running node red, and on the one running the browser if they are not the same. See if either of them is using lots of CPU.

---

<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:** [9 May 2026 15:39 UTC](https://discourse.nodered.org/t/messages-blocked-till-next-deploy/100237/5 "2026-05-09T15:39:42Z")

</div>

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