# Dashboard 2 - ui-template widget receives no further messages after network connection fail and recovery

**URL:** <https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [27 February 2024 14:03 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956 "2024-02-27T14:03:17Z")\
**Posts on this page:** 6\
**Page:** 1

<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:** [27 February 2024 14:03 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/1 "2024-02-27T14:03:17Z")

</div>

Can anyone replicate the issue I am seeing with Dashboard 2 ui-template widgets and temporary network failure? I have submitted [an issue](https://github.com/FlowFuse/node-red-dashboard/issues/619) but I don't know whether this is specific to my template or a general problem. The issue is that if the network connection between the browser and the server fails and then recovers then the widget no longer receives messages from the server.  
If you have a ui-template widget that takes input from received messages then to see if you have the issue, view the dashboard on a different machine to that running node-red. Open the developer console on the dashboard window and disconnect the network so it can no longer communicate with the server. Wait about 10 seconds for connection errors to appear in the console, then reconnect the network. Wait for the re-initialisation messages to appear in the console (only a few seconds) then see whether the widget still responds to messages from the server.

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [27 February 2024 14:19 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/2 "2024-02-27T14:19:53Z")

</div>

I think I see same with leaving dashboard open, and restarting node red. Socket connects and all widgets get initialized - so like for gauges - they still stand on position where connection lost, those values are cleared to defaults. Seems it misses the `replayMessage` on connect and then everything stands still. Even that dev tools show incoming messages from new socket connection.

And ui\_gauge gets updatetes after reconnection. So it's seems ui\_template related issue.

---

<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:** [27 February 2024 15:48 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/3 "2024-02-27T15:48:21Z")

</div>

Yes, now that you point it out, I see that too. I have just noticed that it is not necessary to do a refresh, switching dashboard pages is enough to recover the situation.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [27 February 2024 16:44 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/4 "2024-02-27T16:44:13Z")

</div>

@Colin Could we please use the tag `dashboard-2` for dashboard 2 related posts, instead of `node-red-dashboard-2`

We have used the `dashboard-2` tag since DB2 development first started, and many of us are subscribed to become aware when new posts are made through that tag.  
Also it makes filtering tags much easier when a consistent tag is used.

There are currently over 90 dashboard 2 related posts already tagged `dashboard-2` (which includes some recent ones which I have re-tagged)

> [@Dashboard 2 Beta development](https://discourse.nodered.org/t/dashboard-2-beta-development/83550):
>
> ...Continued from [Dashboard 2.0 Pre-Alpha Available](https://discourse.nodered.org/t/dashboard-2-0-pre-alpha-available/80142) There is also a dashboard-2 tag which you can subscribe to, by going to [Topics tagged dashboard-2](https://discourse.nodered.org/tag/dashboard-2) and then selecting how you wish to be alerted about new posts. [watching]

---

<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:** [27 February 2024 16:59 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/5 "2024-02-27T16:59:37Z")

</div>

Sorry about that, I don't know how it happened, I started typing and that came up as a suggestion, so where it came from I don't know. I have changed it.

---

<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:** [28 March 2024 16:59 UTC](https://discourse.nodered.org/t/dashboard-2-ui-template-widget-receives-no-further-messages-after-network-connection-fail-and-recovery/85956/6 "2024-03-28T16:59:37Z")

</div>

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