# Node catalogue updates seem slower than usual

**URL:** https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827
**Category:** General
**Created:** [24 September 2026 15:16 UTC](https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827 "2026-09-24T15:16:46Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![APXc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/apxc/32/96199_2.png) [@APXc](https://discourse.nodered.org/u/APXc)
#### Post date: [24 September 2026 15:16 UTC](https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827/1 "2026-09-24T15:16:47Z")

</div>

Hi all,

It looks like the Node-RED community node module catalogue is being refreshed less frequently than it used to be.

At the time of writing (14:34 UTC / 16:34 CEST, Thu Sep 24 2026), the catalogue reports:

`Node-RED community node module catalogue — Updated: Thu Sep 24 10:27:47 UTC 2026`

That's roughly 4 hours behind.

As a concrete example, I published a new version of `@yousolution/node-red-contrib-ycs-use-model` to npm at around 10:00 UTC (12:00 CEST), and it still hasn't shown up in the Palette Manager. In the past, updates usually propagated much sooner.

Is this a known issue, or has the update schedule changed?

Thanks!

---

<div class="post-metadata">

### Author: ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [24 September 2026 15:19 UTC](https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827/2 "2026-09-24T15:19:55Z")

</div>

I think you have to add it manually to the catalogue...

---

<div class="post-metadata">

### Author: ![APXc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/apxc/32/96199_2.png) [@APXc](https://discourse.nodered.org/u/APXc)
#### Post date: [24 September 2026 15:26 UTC](https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827/3 "2026-09-24T15:26:19Z")

</div>

Thanks, but it's already there — the module is listed on the Flow Library and shows the new version correctly:

[node-red-contrib-ycs-use-model (node) - Node-RED](https://flows.nodered.org/node/@yousolution/node-red-contrib-ycs-use-model) (v2.0.0)

The Palette Manager on Noderd still shows the previous version (v1.1.1)  
 ![immagine](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/5/c5e73e4683a71141042517ed21c1db2fa8d8d9bf.png)

It used to appear Palete Manager in Node-RED after about an hour.

---

<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: [24 September 2026 15:31 UTC](https://discourse.nodered.org/t/node-catalogue-updates-seem-slower-than-usual/101827/4 "2026-09-24T15:31:07Z")

</div>

> [@APXc](#):
>
> Is this a known issue, or has the update schedule changed?

It's a known issue.

The task that updates the catalogue is scheduled to run as a GitHub action every 30 minutes. In recent weeks, we're lucky if it runs every 4-6 hours.

We're looking at changing how the action is run to not rely on their own scheduler and to trigger it ourselves automatically.
