# 🎉 Node-RED 3.1.0-beta.4 released

**URL:** <https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091>\
**Category:** News\
**Created:** [26 July 2023 16:33 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091 "2023-07-26T16:33:51Z")\
**Posts on this page:** 1\
**Showing post:** 37

<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:** [21 August 2023 07:47 UTC](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091/37 "2023-08-21T07:47:47Z")

</div>

> [@jbudd](#):
>
> I have the same issue with MQTT

It does look like the same problem, after reading your post I realise that opening the config node, clicking Update and deploying makes the error disappear, if I then refresh the browser they come back.

As both you and @gerry are seeing it on 3.02 it isn't a 3.1 beta problem so I will re-open your thread and carry on over there. If anyone has any ideas how to diagnose what is going on then please join us at [When I restart Node-red, or refresh the browser, MQTT broker & nodes show error](https://discourse.nodered.org/t/when-i-restart-node-red-mqtt-broker-nodes-show-error/79081)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-3-1-0-beta-4-released/80091)._