# 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:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 15:50 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/41 "2019-08-08T15:50:22Z")

</div>

any further thoughts @knolleary

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [8 August 2019 15:57 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/43 "2019-08-08T15:57:50Z")

</div>

Hi @nodecentral, I appreciate this is inconvenient to you and I've already spent some time getting more debug information from you. But this is not the only thing I have to work on.

As I've said a few times, I have no idea what is happening. You must be hitting a bug somewhere, but I don't know what and nor have I dropped everything else I am doing to chase it down. Given you are the only person apparently hitting it, then I can't rule out there being something particular about your setup which is causing this - I just don't have any ideas what that could be.

There is one more thing you could look at.

In the chrome developer tools there is the 'network' tab. If you have that open when you click the Deploy button that first time, then you should see a new entry appear in the network request table. Click on it and you should be able to see the response the runtime returned - it should have a `rev` property. Compare that to the result of `RED.nodes.version()` and what is logged by the runtime.

This won't give an answer - it'll just be another data point to consider when I shift my focus to this issue.

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 17:26 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/44 "2019-08-08T17:26:31Z")

</div>

> [@knolleary](#):
>
> I appreciate this is inconvenient to you and I've already spent some time getting more debug information from you. But this is not the only thing I have to work on

@knolleary (Nick) I totally understand, and i'm very greatful for your assistance - I just want to provide as much information as I can to help you/others debug this.

Hopefully the following helps.

With this prompt up

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/8bab8e840282128d2e4f10749e20285d3aa050a3.png)

The last entry on the network tab is this..

```auto
{flows: [{id: "d83cca46.b39338", type: "tab", label: "Flow 1", disabled: false, info: ""},…],…}
flows: [{id: "d83cca46.b39338", type: "tab", label: "Flow 1", disabled: false, info: ""},…]
rev: "bb54f85a5ff7e6d152a25f0895c54aa1"

```

.. and the RED.nodes.version() is this.

```auto
"8aa3c3bbce1629e7d3391b91908dca23"

```

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 17:35 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/45 "2019-08-08T17:35:18Z")

</div>

Follow on, not sure if this helps.

If I choose then "Merge" - it brings the two version numbers inline (Rev under Network and version under the Console).. but the "Deploy" button is still active/highlighted

If I click Deploy, it says "Succesffull", and the Network view adds 3 lines

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/8/8f97d6bc98e3c82a8c5dc1e5255ee47a235b57d6.png)

The last one in the list "flows" shows

```auto
{}
No properties

```

---

<div class="post-metadata">

**Author:** ![realjax](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/realjax/32/895_2.png) [@realjax](https://discourse.nodered.org/u/realjax)\
**Post date:** [8 August 2019 17:35 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/46 "2019-08-08T17:35:49Z")

</div>

But... do you still have node-red-harmony-websocket installed? If so have you tried uninstalling it to see if the problem goes away?

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 17:38 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/47 "2019-08-08T17:38:02Z")

</div>

I could try (but to be clear I have that add-on installed in other set ups with no issue)  
How do i do that with this one - there is no 'uninstall" option in the pallette ?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [8 August 2019 17:45 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/48 "2019-08-08T17:45:26Z")

</div>

> [@nodecentral](#):
>
> The last entry on the network tab is this..

I _think_ you are showing us the data that was sent in the request, not the response that was returned.

1. make sure the network tab is open _before_ you press deploy
2. press deploy and you _should_ see a new entry appear - make sure it is that one you click on.
3. then make sure you click the 'Response' tab in the subwindow:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/0b03d2e9c1da07e83084d227dbe0fbf31021b785.png)

---

<div class="post-metadata">

**Author:** ![realjax](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/realjax/32/895_2.png) [@realjax](https://discourse.nodered.org/u/realjax)\
**Post date:** [8 August 2019 17:46 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/49 "2019-08-08T17:46:46Z")

</div>

You should be able to run

npm uninstall node-red-harmony-websocket

Run it inside your .node-red folder.  
The fact that the plugin works fine in a diff. Nodered instance proves nothing btw.

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 19:31 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/50 "2019-08-08T19:31:01Z")

</div>

> [@realjax](#):
>
> npm uninstall node-red-harmony-websocket

I ran the command, to uninstall "node-red-contrib-harmony-websocket" and it has stopped the messages???!!! (@realjax - I shouldn’t have doubted you, and just tried it 🙂 )

I can now add/move/change nodes and do deployments with no server update message (so far)

I wonder what the hell that Harmony add-on was doing and why do I not see it elsewhere I have it. (I’d still like to get the root cause as I’d still like to use that add-on)

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [8 August 2019 19:33 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/51 "2019-08-08T19:33:11Z")

</div>

Please open an issue on the nodes github page to flag the issue to the nodes author

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [8 August 2019 19:35 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/52 "2019-08-08T19:35:29Z")

</div>

> [@nodecentral](#):
>
> node-red-contrib-harmony-websocket

> [@ukmoose](#):
>
> Please open an issue on the nodes github page to flag the issue to the nodes author

Looks like others already have - [Merge required when I change anything · Issue #3 · lopelex/node-red-contrib-harmony · GitHub](https://github.com/lopelex/node-red-contrib-harmony/issues/3)

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 19:56 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/53 "2019-08-08T19:56:58Z")

</div>

Many thanks @knolleary and @realjax ,

I’ve added my comments (along with a link to this post in the github entry) hopefully it can be fixed soon.

_It’s just strange that I don’t see the same issue on my other NR instance which has the Harmony add-on installed 🤔_

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [8 August 2019 20:08 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/54 "2019-08-08T20:08:17Z")

</div>

And do those instances use the latest version of harmony websocket ?  
Anyway I won't upgrade it until it is fixed 😉

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [8 August 2019 20:53 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/55 "2019-08-08T20:53:17Z")

</div>

> [@bakman2](#):
>
> do those instances use the latest version of harmony websocket ?

Now that we have something specific to focus upon, looking at the instances where the Harmony web-socket add-on is working (no update messages); They are not on the latest.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/e/e0eb876e2e2f47c80165cbacf6dc0d8ded920b4a.jpeg)

@bakman2 what version are you running (without issue) ?

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [8 August 2019 20:57 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/56 "2019-08-08T20:57:10Z")

</div>

Same version. It must be caused by the latest commit.

---

<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:** [9 August 2019 07:28 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/57 "2019-08-09T07:28:28Z")

</div>

@nodecentral you could try installing the previous version and see if it is ok, that will confirm that it is just the latest release that has the problem.

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [9 August 2019 08:57 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/58 "2019-08-09T08:57:05Z")

</div>

> [@Colin](#):
>
> you could try installing the previous version

Not done that before, how do you do that, only the latest one is in the palette?

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [9 August 2019 09:02 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/59 "2019-08-09T09:02:01Z")

</div>

You can check the available versions:

`npm view node-red-contrib-harmony-websocket versions`

and install with

`npm install node-red-contrib-harmony-websocket@<version number>`

---

<div class="post-metadata">

**Author:** ![nodecentral](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nodecentral/32/10432_2.png) [@nodecentral](https://discourse.nodered.org/u/nodecentral)\
**Post date:** [9 August 2019 10:10 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/60 "2019-08-09T10:10:36Z")

</div>

Thanks @bakman2

> [@bakman2](#):
>
> install with
> 
> `npm install node-red-contrib-harmony-websocket@<version number>`

All done, I wasn't sure it had installed at first (various warnings), but after doing a stop-start of NR, it appeared, and so far so good - no server updated messages. 👍

---

<div class="post-metadata">

**Author:** ![lopelex](https://avatars.discourse-cdn.com/v4/letter/l/e99b99/32.png) [@lopelex](https://discourse.nodered.org/u/lopelex)\
**Post date:** [15 August 2019 10:13 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/61 "2019-08-15T10:13:20Z")

</div>

The error is found and fixed, hopefully. Try the new version.

> <https://github.com/lopelex/node-red-contrib-harmony/issues/3>

  
Deleting the node.hub object was not a good idea.  

> <https://github.com/lopelex/node-red-contrib-harmony/blob/master/harmony/harmony-server.js#L58>

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

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