# Node registration order

**URL:** <https://discourse.nodered.org/t/node-registration-order/6779>\
**Category:** General\
**Created:** [14 January 2019 08:51 UTC](https://discourse.nodered.org/t/node-registration-order/6779 "2019-01-14T08:51:54Z")\
**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:** [14 January 2019 08:57 UTC](https://discourse.nodered.org/t/node-registration-order/6779/2 "2019-01-14T08:57:39Z")

</div>

> [@Lionel](#):
>
> So, the question is, can I force the registration node order ?

When the runtime starts your flows, it first looks for all configuration nodes and starts them. It tries to identify any dependencies between the config nodes and will start them in the right order to satisfy those dependencies. It then starts the regular flow nodes, one tab at a time, in the order they were added to the tab.

If you have a node that other nodes depend on, I would assume its a config node - as regular flow nodes don't, in general, have dependencies on each other like that.

If your node is a config node, and other nodes declare a dependency on it, then it will get started first.

---

_[View the full topic](https://discourse.nodered.org/t/node-registration-order/6779)._