# When are config nodes defined in the flow editor?

**URL:** <https://discourse.nodered.org/t/when-are-config-nodes-defined-in-the-flow-editor/73769>\
**Category:** Developing Nodes\
**Created:** [16 January 2023 17:24 UTC](https://discourse.nodered.org/t/when-are-config-nodes-defined-in-the-flow-editor/73769 "2023-01-16T17:24:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [16 January 2023 17:44 UTC](https://discourse.nodered.org/t/when-are-config-nodes-defined-in-the-flow-editor/73769/2 "2023-01-16T17:44:06Z")

</div>

> [@Help button in node properties](https://discourse.nodered.org/t/help-button-in-node-properties/73727/11):
>
> I am still trying to determine if that is a bug or just the expected behavior.

`onpaletteadd` is called when the node is added to the palette. That happens before the current flow configuration is loaded. So it is entirely expected that `eachConfig` wouldn't return anything for code called in `onpaletteadd`.

> [@tve](#):
>
> Again, your best bet may be to describe what you use `eachConfig` for 'cause perhaps there's a different solution.

Indeed. Is this really a one-time only action you want to run, or something you need to do whenever a new config node of a particular type is added/import or removed?

---

_[View the full topic](https://discourse.nodered.org/t/when-are-config-nodes-defined-in-the-flow-editor/73769)._