# Problems updating flows to latest Dashboard Version

**URL:** https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145
**Category:** Dashboard
**Created:** [14 September 2018 15:38 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145 "2018-09-14T15:38:23Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![mapos](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mapos](https://discourse.nodered.org/u/mapos)
#### Post date: [14 September 2018 15:38 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/1 "2018-09-14T15:38:23Z")

</div>

Hi,

im actually facing problems updating esisting flows with ui to the latest dashboard version.

the problem shows-up as a continuos connection-lost message and impossibility to use the ui.  
no errors however shown in logs.

also unuseful to clear the cash  
it happens with chrome on windows 10, and also with chrome and safari on iOS.

the only solution seems to be re-create groups and reinsert widgest and components.  
this is of course a very very cumbersome process considering the number of dashboard components i have in previous flows (dashboard version 2.6.1 and NR 0.19.3).

has anyone faced the same problem? any smart solution to this migration?  
thanks

M

---

<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: [14 September 2018 15:54 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/2 "2018-09-14T15:54:06Z")

</div>

You probably just need to flush the browser cache - force a reload. Usually Ctrl-R a couple of times does it.

---

<div class="post-metadata">

### Author: ![mapos](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mapos](https://discourse.nodered.org/u/mapos)
#### Post date: [14 September 2018 16:16 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/3 "2018-09-14T16:16:31Z")

</div>

Tried already,  
also F5.... and clear browsing data....same ..

---

<div class="post-metadata">

### Author: ![mapos](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mapos](https://discourse.nodered.org/u/mapos)
#### Post date: [17 September 2018 10:47 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/4 "2018-09-17T10:47:37Z")

</div>

Could be this happen because we have ui also in subflows?

---

<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: [17 September 2018 11:20 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/5 "2018-09-17T11:20:48Z")

</div>

The dashboard does not support having its nodes inside subflows. You will get very unpredictable results when it comes to the layout.

---

<div class="post-metadata">

### Author: ![mapos](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mapos](https://discourse.nodered.org/u/mapos)
#### Post date: [17 September 2018 13:26 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/6 "2018-09-17T13:26:15Z")

</div>

Ok likely that's the problem  
thx

---

<div class="post-metadata">

### Author: ![mapos](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@mapos](https://discourse.nodered.org/u/mapos)
#### Post date: [26 September 2018 22:53 UTC](https://discourse.nodered.org/t/problems-updating-flows-to-latest-dashboard-version/3145/7 "2018-09-26T22:53:49Z")

</div>

Just to inform that we found out the problem was due to some NR misalignement  
we run a clean new installation and old ui work perfectly...
