# Different Set of Flows at Each Reboot

**URL:** <https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277>\
**Category:** General\
**Created:** [7 August 2020 15:19 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277 "2020-08-07T15:19:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![stokes776](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stokes776/32/66036_2.png) [@stokes776](https://discourse.nodered.org/u/stokes776)\
**Post date:** [7 August 2020 15:19 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277/1 "2020-08-07T15:19:01Z")

</div>

Hello,

Looking for a bit of guidance here. I have an Ubuntu server running Node-Red. Each time I reboot it, I seem to randomly get one or the other, set of Flows.

For example, before reboot I have the following flows:  
\_Default , Site1, Site2, Testing

After reboot  
\_Default , Flow1, Flow2

The second set of flows, is recognizable and has elements I DID add at one point, but was a long time ago.

I would guess Node-Red is somehow loading a flows.json and then saying, yep im done. But then other reboots it loads the first set of flows as desired.

How do I control which set of flows get loaded?

---

<div class="post-metadata">

**Author:** ![stokes776](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stokes776/32/66036_2.png) [@stokes776](https://discourse.nodered.org/u/stokes776)\
**Post date:** [7 August 2020 15:21 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277/2 "2020-08-07T15:21:15Z")

</div>

I just noticed too, that on the first set I show NodeRed at v1.0.3.

On the second set I have NodeRed at v1.0.6

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [7 August 2020 15:41 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277/3 "2020-08-07T15:41:25Z")

</div>

two possibilities

1. you are running as a different user so picking up a different Node-RED install and flow
2. your computer is changing hostname (maybe via dhcp but this doesn't usually happen on ubuntu) - and so picking up a different flow in ~/.node-red .

---

<div class="post-metadata">

**Author:** ![stokes776](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stokes776/32/66036_2.png) [@stokes776](https://discourse.nodered.org/u/stokes776)\
**Post date:** [7 August 2020 15:43 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277/4 "2020-08-07T15:43:41Z")

</div>

Thank you, I figured it out. At some point I must have installed Node-Red with Snap package manger. SO you are correct, two Node-Reds were running, one at 1.06 and one via the npm.

sudo snap list was able to show me the installed Node-Red instance via snap.

Sudo snap remove node-red removed that install.

---

<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:** [21 August 2020 15:43 UTC](https://discourse.nodered.org/t/different-set-of-flows-at-each-reboot/31277/5 "2020-08-21T15:43:45Z")

</div>

Closed on 21 August 2020 15:43 UTC

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