# 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:** 2

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

</div>

> [@knolleary](#):
>
> 1. edit your settings file and set the logging level to `debug` .
> 2. restart Node-RED
> 3. In the log, you should have a line that says something like:
> 
> ```auto
> 6 Aug 09:53:27 - [debug] loaded flow revision: 2f1f470b70250648fd589a2794afc0f0
> 
> ```

Ok, seems my Chrome Browser is locked down due to a work/management configuration. I do not even have a View menu option ?

Is there another way to check - I can right click and select ‘Inspect’ ?

What I can share is the log information

```auto
7 Aug 17:57:06 - [debug] loaded flow revision: c2e586b3e5ff5ad8c7ca0592107fee01

```

---

<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:** [7 August 2019 17:32 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/22 "2019-08-07T17:32:40Z")

</div>

If you can 'inspect' then you should be able to switch to the console tab of the developer tools window it opens.

---

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

</div>

Yah - here it is !!

> RED.nodes.version()
> 
> "c2e586b3e5ff5ad8c7ca0592107fee01"

---

<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:** [7 August 2019 17:36 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/24 "2019-08-07T17:36:58Z")

</div>

When I hit the refresh and get the prompt - I see this..

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

OK, now after refreshing the browser and getting the update on server message I see this a different flow version ?

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

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

---

<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:** [7 August 2019 17:42 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/25 "2019-08-07T17:42:44Z")

</div>

> [@knolleary](#):
>
> RED.nodes.version()

And now its back to the original one again

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

---

<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:** [7 August 2019 17:44 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/26 "2019-08-07T17:44:59Z")

</div>

The log shows the two versions

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

---

<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:** [7 August 2019 17:47 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/27 "2019-08-07T17:47:37Z")

</div>

In one of your screenshots it shows an error message with POST 409 Conflict - does that happen whenever you open the editor?

---

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

</div>

You logs show the flows stopping and starting - is that something you are doing? Are you deploying changes manually?

---

<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:** [7 August 2019 17:58 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/29 "2019-08-07T17:58:34Z")

</div>

> [@knolleary](#):
>
> In one of your screenshots it shows an error message with POST 409 Conflict - does that happen whenever you open the editor?

I can't seem to recreate that again at the moment..

> [@knolleary](#):
>
> You logs show the flows stopping and starting - is that something you are doing? Are you deploying changes manually?

All I'm doing is either hitting Deploy or doing a browser refresh ?

---

<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:** [7 August 2019 18:00 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/30 "2019-08-07T18:00:47Z")

</div>

OK, I can recreate that Post error. here you go

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

If I choose ignore, then move a node, and hit deploy - I get the error again.

If I choose merge, I have to hit deploy again, but it's then successfull - but the flow version changes

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

---

<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:** [7 August 2019 18:05 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/31 "2019-08-07T18:05:45Z")

</div>

Update of the logs

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

---

<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:** [7 August 2019 18:19 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/32 "2019-08-07T18:19:14Z")

</div>

Every time you hit deploy you are changing things. It is adding noise to the logs for the issue we are trying to focus on. The 409 is a normal 'error' when you hit deploy but your flows are out of date.

Please follow the steps I described:

1. Restart Node-RED and note the logged flow revision.
2. Reload the editor. Do you get the notification? Do not click on any button. Get the node version from the console.

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [8 August 2019 08:18 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/33 "2019-08-08T08:18:59Z")

</div>

FWIW,

I had a similar problem recently and tracked it down to the 'node-red-harmony-websocket' node I had installed. Removed the node and all has been OK since.

Colin

---

<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 09:33 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/34 "2019-08-08T09:33:06Z")

</div>

> [@mudwalker](#):
>
> I had a similar problem recently and tracked it down to the 'node-red-harmony-websocket' node I had installed. Removed the node and all has been OK since.

Interesting, but I have the 'node-red-harmony-websocket' working on another NR instance - and I don't see this same 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 09:41 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/35 "2019-08-08T09:41:19Z")

</div>

> [@knolleary](#):
>
> - Restart Node-RED and note the logged flow revision.

Check (done)

- ran node-red-stop
- closed browser tab
- ran node-red-start
- screenshot below of start up/log - showing loaded flow revision

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

> [@knolleary](#):
>
> - Reload the editor. Do you get the notification? Do not click on any button. Get the node version from the console.

- Loaded NR editor into a new browser tab, no error/notification seen
- Typed in "RED.nodes.version()" into the console (via Inspect) - screensnippet below

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

Both report the same version/number

---

<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 09:45 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/36 "2019-08-08T09:45:09Z")

</div>

If both are the same, and you don't get the notification, then everything is working and sharing screenshots of it working are not that helpful.

I thought you said you got the notification every time you opened the editor.

So what we need is a precise set of steps you take that leads you to hitting the notification.

---

<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 09:54 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/37 "2019-08-08T09:54:03Z")

</div>

> [@knolleary](#):
>
> I thought you said you got the notification every time you opened the editor.

Not the opening, it's appears during deployment and/or browser refreshes (mainly the latter)

OK, as I've not done anything since the above post - these steps give me the flows on server message.

1. A browser refresh now (with nothing deployed) = no message
2. Move a node slightly to a different location to bring up the Deploy option, hit deploy - "change successful" no other message
3. Do a browser refresh - I get the message come up. "The flows on the server have been updated"
4. The flow versions in the log and the browser console are the same (different from earlier, but the same as I had done a deploy\_
5. If I select do a review, it says "The server is running a more recent set of flows"
6. Going into "Review Changes" - everything listed is "unchanged"

I then choose "Merge" it returns me to the editor again.

If I then do a browser fresh again, it get the same message that the "flows on the server have been updated" message again

---

<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 09:56 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/38 "2019-08-08T09:56:45Z")

</div>

> [@nodecentral](#):
>
> - A browser refresh now (with nothing deployed) = no message
> - Move a node slightly to a different location to bring up the Deploy option, hit deploy - "change successful" no other message

What does the `RED.nodes.version()` command return after the Deploy but _before_ your reload the editor?

---

<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 10:01 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/39 "2019-08-08T10:01:41Z")

</div>

OK, not doing anything more (other than where I got to in the steps shared above) every browser refresh I do will give me this error.

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

I'm going to stop-start NR again - so I can do a browser refresh where no messages come up and then I'll try what you;ve asked

---

<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 10:10 UTC](https://discourse.nodered.org/t/recurring-the-flows-on-the-server-have-been-updated-message/13885/40 "2019-08-08T10:10:07Z")

</div>

Ok, NR restarted..

FYI - After a restart I can referesh the the NR config page on the browser as many times as I like - no message comes up.

- Checking the flow revisions - they are the same (in the log and via the console)
- Just moved a node slightly to a different location to bring up the Deploy option, hit deploy - "change successful" no other message
- A new "saved flow revision" is recorded in the log
- The version reported via the console in the browser has not changed, it is still the earlier one.

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

So the log and the console versions are different....

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

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