# Flow library stuck again?

**URL:** <https://discourse.nodered.org/t/flow-library-stuck-again/74329>\
**Category:** General\
**Created:** [29 January 2023 02:22 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329 "2023-01-29T02:22:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tve](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tve/32/59475_2.png) [@tve](https://discourse.nodered.org/u/tve)\
**Post date:** [29 January 2023 02:22 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/1 "2023-01-29T02:22:11Z")

</div>

I added and updated repos in the flow library 40 minutes ago and they still don't show up in the catalogue. Is the library updater stuck again?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 January 2023 02:55 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/2 "2023-01-29T02:55:38Z")

</div>

Not to say I am smarter than you, but I have been caught on a similar problem myself.

How do you know they aren't updated?

Are you looking on the webpage/gui or from a CLI?

(Sorry. Not to seem like I am _baiting_ you.)

Force a refresh on the browser if you are doing it that way.  
That caught me big time a while ago.

---

<div class="post-metadata">

**Author:** ![tve](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tve/32/59475_2.png) [@tve](https://discourse.nodered.org/u/tve)\
**Post date:** [29 January 2023 03:00 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/3 "2023-01-29T03:00:29Z")

</div>

Now they _finally_ updated...  
The way I look:

```auto
curl 'https://catalogue.nodered.org/catalogue.json' | \
  sed 's/},{/},\\n{/g' | \
  egrep 'node-red-(fd|flexdash)'

```

(Using jq instead of sed would be more elegant but I always have to look up the manual...)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 January 2023 03:04 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/4 "2023-01-29T03:04:44Z")

</div>

Good to hear all worked out.

As i said: I wasn't wanting to _show you up_ or anything.  
I was just running in circles a while ago because I only `refreshed` the browser when should have `force refreshed` it.

---

<div class="post-metadata">

**Author:** ![tve](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tve/32/59475_2.png) [@tve](https://discourse.nodered.org/u/tve)\
**Post date:** [29 January 2023 03:08 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/5 "2023-01-29T03:08:26Z")

</div>

It wasn't a browser refresh issue or so, the catalogue wasn't being updated. Probably again only runs once an hour 😢  
Teaches me to try and push stuff to the flow library, best leave it out and be done with that...

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [29 January 2023 03:09 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/6 "2023-01-29T03:09:38Z")

</div>

Yeah, ironic that the faster computers seem to get the more patient you have to be with them.  
😉  
I'm sure you remember computers in the 80's.  
(Well, guessing.)

---

<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:** [29 January 2023 08:29 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/7 "2023-01-29T08:29:24Z")

</div>

> [@tve](#):
>
> Teaches me to try and push stuff to the flow library, best leave it out and be done with that..

I'm not sure what you mean here. Why is leaving something out the best option?

The flow library catalog refreshes every 30 minutes. That's how it has pretty much always worked dating back to when it used to scan npm for updates automatically. Because the scan for updates was a very costly operation, we avoided running that too often.

Given how unreliable the npm API became for this, we scrapped the scanning and left it to users to manually add/update their nodes. However the task to regenerate the catalog has remained on that 30 min schedule.

It would be feasible to change it to refresh automatically when a nodes is added/updated. Just needs getting done.

---

<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:** [30 March 2023 08:29 UTC](https://discourse.nodered.org/t/flow-library-stuck-again/74329/8 "2023-03-30T08:29:54Z")

</div>

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