# NR requires multiple browser refreshes to load flows - again

**URL:** <https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846>\
**Category:** General\
**Created:** [19 May 2022 12:10 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846 "2022-05-19T12:10:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![alex88](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alex88/32/55523_2.png) [@alex88](https://discourse.nodered.org/u/alex88)\
**Post date:** [19 May 2022 12:10 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/1 "2022-05-19T12:10:57Z")

</div>

I am getting the same symptoms as with the issue described here:

> [@NR requires multiple browser refreshes to load flows](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows/61478):
>
> Hi, I've had this pesky issue for months now. The only significant change has been that I have moved all my Environments from Windows to Debian 11 and Raspbian. The issue is that quite often flows will not load fully load without manual refreshes. On loading a flow, I get this screen instead: [image] If I refresh the page as soon as I see it, I will then have to refresh 2x or 3x times in total before the progress bar fully completes and the flows are visible and ready to use. If I wait …

And this from the console log:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/9/896e86077ae1a898aad85ee326d59e8eab8047ef.png)

Running v3.0.0 beta 2

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [19 May 2022 12:14 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/2 "2022-05-19T12:14:22Z")

</div>

Can I suggest that you delete and repost this on the beta thread if you think this is a beta issue

---

<div class="post-metadata">

**Author:** ![alex88](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alex88/32/55523_2.png) [@alex88](https://discourse.nodered.org/u/alex88)\
**Post date:** [19 May 2022 12:36 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/3 "2022-05-19T12:36:04Z")

</div>

Sure, do you mean this one?

> [@tada Node-RED 3.0.0-beta.2 released](https://discourse.nodered.org/t/node-red-3-0-0-beta-2-released/62698/21):
>
> I don't think so, if you look at the dashed swipe track line, you'll see I curved it's path between the 2 crossed lines, but yes, maybe it was a little close. I think that the bigger problem is trying to perform a 'consistent speed' swipe using a touchpad, whilst holding down a touchpad button, and the keyboard combination at the same time. It isn't easy! and results in wires being missed because the cursor travelled too fast over a particular section of the swipe. But, not a big problem, let…

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [19 May 2022 12:36 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/4 "2022-05-19T12:36:54Z")

</div>

yes please 🙂  
..................

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [19 May 2022 12:54 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/5 "2022-05-19T12:54:51Z")

</div>

But it be handy if you could check to see if issue happens using NR stable version before doing that 🙂

---

<div class="post-metadata">

**Author:** ![alex88](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alex88/32/55523_2.png) [@alex88](https://discourse.nodered.org/u/alex88)\
**Post date:** [19 May 2022 13:36 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/6 "2022-05-19T13:36:16Z")

</div>

I have just replicated it on v2.2 on another NR ENV

I did an "empty cached and hard reload" on the browser a few days ago and it seemed to fix it, but it is coming up again - intermittently

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [19 May 2022 19:11 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/7 "2022-05-19T19:11:22Z")

</div>

Do you have an anti-malware tool installed? Also, I assume that the Chrome extension that seemed to be causing the issue last time hasn't crept back in?

Some google-fu seems to suggest that something else is interfering with the browser cache.

---

<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:** [18 July 2022 19:11 UTC](https://discourse.nodered.org/t/nr-requires-multiple-browser-refreshes-to-load-flows-again/62846/8 "2022-07-18T19:11:30Z")

</div>

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