# Recurring "The flows on the server have been updated" message

**URL:** <https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885>\
**Category:** General\
**Created:** [31 July 2019 23:16 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885 "2019-07-31T23:16:46Z")\
**Posts on this page:** 10\
**Page:** 4

<div class="post-metadata">

**Author:** ![OrlandodaSilva](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/orlandodasilva/32/33879_2.png) [@OrlandodaSilva](https://discourse.nodered.org/u/OrlandodaSilva)\
**Post date:** [18 December 2020 09:41 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/62 "2020-12-18T09:41:53Z")

</div>

Good day. I had  
"the flows on the server have been updated" notice, when no update had taken place, combined with an error about a missing node called "Server" which as far as I know I have never installed.

My fix was to look at all my installed nodes in my pallet and update the ones that had a update notification next to them. This required a restart of node-red after which the notices no longer appeared.

I believe it is the equivalent of the above suggestions without using the command line.

I had previously restarted Node-red (power cycle), restarted my browser and PC. With no effect.

I am running Node-red on a Android TV box with Termux.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [18 December 2020 10:58 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/63 "2020-12-18T10:58:47Z")

</div>

I've found this happens when I open a window to the editor. Then after awhile, I open a second window (could even be in another browser) and make a change to sometging and deploy. Then I go back to the first window and there is the message. In this image you can see I moved a `debug` node and deployed and you can see the message on the other window,

 ![Screen Shot 2020-12-18 at 5.56.16 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/c/dc1073fdab47a67691e566963ccb11cbdd3b4168.png)

I've learned that when I see that message, I've got too many windows open 🤪

---

<div class="post-metadata">

**Author:** ![danielbrunt57](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/danielbrunt57/32/42815_2.png) [@danielbrunt57](https://discourse.nodered.org/u/danielbrunt57)\
**Post date:** [13 April 2021 23:30 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/64 "2021-04-13T23:30:32Z")

</div>

After the recent rounds of updates (HA, Node-RED, etc., etc.) I started having this issue with one and only one window open. After a lot of searching, digging, checking, etc., etc. what finally fixed it for me was uninstalling & re-installing the Node-RED addon in HA.

---

<div class="post-metadata">

**Author:** ![smanjunath211](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/smanjunath211/32/95742_2.png) [@smanjunath211](https://discourse.nodered.org/u/smanjunath211)\
**Post date:** [2 November 2021 15:47 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/65 "2021-11-02T15:47:55Z")

</div>

I started having same issue, i am sure i have only one node-red instance running using as a window service (nssm). no browser editor open in any connected computers.  
any changes in the only open browser editor, i get a message when i try to deploy that the flow on servers have been updated, and asks me whether to merge .and upon doing (or not doing also) i see that the changes do not appear on the dashboard, i have to restart the node-red service to make effect of the changes. I am confused.

i am confused.

---

<div class="post-metadata">

**Author:** ![johnniepop](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnniepop/32/67539_2.png) [@johnniepop](https://discourse.nodered.org/u/johnniepop)\
**Post date:** [6 October 2022 12:43 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/66 "2022-10-06T12:43:15Z")

</div>

Hi,

Let me give my two cents on this topic and a fairly different perspective.

I'm running two applications on GCP Cloud Run. They're both pairs - a Dashboard application showing sensory data, and the accompanying admin console - the Node-RED editor responsible for building the Dashboard in every pair.  
After deploying the two containers both pairs of applications started to act quirky - the Dashboards refreshed on every 15 to 30 seconds whereas the admin consoles started to show the popups this thread is dedicated to.  
Using only one of the apps in the browser didn't change anything ...

What worked in my case? I just increased the container resources:

- CPU : 1 \> 2
- Memory: 512 MiB \> 2048 GiB

After the redeployment I never got the same problem again, even when using the for applications in separate tabs simultaneously.

So what can you make out of this?

Cheers!

---

<div class="post-metadata">

**Author:** ![paulkeates](https://avatars.discourse-cdn.com/v4/letter/p/9de053/32.png) [@paulkeates](https://discourse.nodered.org/u/paulkeates)\
**Post date:** [6 October 2022 12:48 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/67 "2022-10-06T12:48:54Z")

</div>

Hi,

My experience (not with Docker but apps like this in general & VM's): it was most likely the additional RAM that resolved the issue, not the additional CPU.

I bet there is a threshold / magic value that Node needs to operate 'correctly'. I know there are some Node-RED specific options for small-memory systems (Raspberry Pi) that allow overriding memory limits.

Cheers,

Paul

---

<div class="post-metadata">

**Author:** ![johnniepop](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/johnniepop/32/67539_2.png) [@johnniepop](https://discourse.nodered.org/u/johnniepop)\
**Post date:** [6 October 2022 12:53 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/68 "2022-10-06T12:53:12Z")

</div>

Indeed. Watching the Cloud Run metrics after the redeployment showed exactly that. I'm sure it would be satisfied even by 1 GiB of memory allocation.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [6 October 2022 18:02 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/69 "2022-10-06T18:02:02Z")

</div>

> [@johnniepop](#):
>
> CPU : 1 \> 2

This will make no real difference. Nodejs is single threaded.

---

<div class="post-metadata">

**Author:** ![SveinHa](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sveinha/32/71169_2.png) [@SveinHa](https://discourse.nodered.org/u/SveinHa)\
**Post date:** [25 December 2023 17:51 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/70 "2023-12-25T17:51:54Z")

</div>

Just to add a bit of my experience.

I have been using "node-red-contrib-harmony" for years with no issues. About one week ago, I deleted all used nodes in my flow since they were not in use any more and some time later, I got the "The flows on the server have been updated" message quite frequently, just minutes between, and only one browser active. To see if it was a browser problem, I switched from Brave to Firefox but that was exactly the same.

I also noted, in the system log, this message on NodeRed startup:

> "error: Error: connect ECONNREFUSED 172.16.0.91:5222"

172.16.0.91 was my Harmony hub but this IP is now taken for another unit.

After removing the "node-red-contrib-harmony" from my palette, the problem disappeared.

---

<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:** [25 December 2023 19:28 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/71 "2023-12-25T19:28:35Z")

</div>

Is your node red accessible via the Internet? If so then you have been hacked.

[Previous page](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885.md?page=3)