# How long from publishing new module version to it showing up in palette manager?

**URL:** <https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170>\
**Category:** Developing Nodes\
**Created:** [10 September 2023 05:23 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170 "2023-09-10T05:23:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mountaindude](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mountaindude/32/27713_2.png) [@mountaindude](https://discourse.nodered.org/u/mountaindude)\
**Post date:** [10 September 2023 05:23 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170/1 "2023-09-10T05:23:05Z")

</div>

This was discussed [here](https://discourse.nodered.org/t/how-long-can-it-take-for-a-node-to-show-up-as-an-installable-package-in-the-palette/35929/5) already, with the answer that the palette mgr updates every 30 minutes.

Over the last week or so I've however regularly seen update times of many hours, and now with the latest version of my @ptarmiganlabs/ctrl-q-nr module it's been over two days since 0.1.1 was published, but it still doesn't show in the palette manager.  
I've restarted node-red, reloaded the browser, tried on four different computers/browsers, nothing.

Latest version is now 0.1.3: [ctrl-q-nr (node) - Node-RED](https://flows.nodered.org/node/@ptarmiganlabs/ctrl-q-nr)

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

Ideas?

---

<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:** [10 September 2023 08:28 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170/2 "2023-09-10T08:28:21Z")

</div>

Since April 2020 the flow library doesn't automatically refresh. A refresh has to be requested.

[https://nodered.org/docs/creating-nodes/packaging#adding-to-flowsnoderedorg](https://nodered.org/docs/creating-nodes/packaging#adding-to-flowsnoderedorg)

---

<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:** [10 September 2023 08:32 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170/3 "2023-09-10T08:32:05Z")

</div>

Ah - but there was a genuine issue blocking the catalogue refresh. Have poked it - normal service should be restored.

---

<div class="post-metadata">

**Author:** ![mountaindude](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mountaindude/32/27713_2.png) [@mountaindude](https://discourse.nodered.org/u/mountaindude)\
**Post date:** [10 September 2023 09:36 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170/4 "2023-09-10T09:36:38Z")

</div>

Yeah I had done the manual step to request updates for the new module version (that's not a bad thing btw, makes you double check things before requesting an update).

...and your poke seems to have done the trick.  
Thanks!

---

<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:** [24 September 2023 09:36 UTC](https://discourse.nodered.org/t/how-long-from-publishing-new-module-version-to-it-showing-up-in-palette-manager/81170/5 "2023-09-24T09:36:59Z")

</div>

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