# Log level for "Waiting for missing types to be registered" should be 'warn' or 'error'

**URL:** <https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354>\
**Category:** Core Development\
**Created:** [15 August 2019 13:58 UTC](https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354 "2019-08-15T13:58:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![deme](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@deme](https://discourse.nodered.org/u/deme)\
**Post date:** [15 August 2019 13:58 UTC](https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354/1 "2019-08-15T13:58:13Z")

</div>

Hey,

after installing a new node, node-red did not come up. Looking at the log-files did not give me any clues... only after changing the log-level to 'info' I identified the cause:

> Aug 15 11:39:52 myHost nodered[27265]: 15 Aug 11:39:52 - [info] Waiting for missing types to be registered:  
> Aug 15 11:39:52 myHost nodered[27265]: 15 Aug 11:39:52 - [info] - [name of node]

In my opinion: something that stops node-red from properly starting should be flagged at least with 'warn' or 'error' in the log files.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [15 August 2019 15:02 UTC](https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354/2 "2019-08-15T15:02:29Z")

</div>

Well the editor also shows that the flows are stopped and that a fix is required.

---

<div class="post-metadata">

**Author:** ![afelix](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/afelix/32/9743_2.png) [@afelix](https://discourse.nodered.org/u/afelix)\
**Post date:** [15 August 2019 16:43 UTC](https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354/3 "2019-08-15T16:43:23Z")

</div>

Yes, the editor might show it, but having the log give more or less a warning, the log type for that line should reflect it, regardless of what log level you have to set or where else you can see this information.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [15 August 2019 17:41 UTC](https://discourse.nodered.org/t/log-level-for-waiting-for-missing-types-to-be-registered-should-be-warn-or-error/14354/4 "2019-08-15T17:41:35Z")

</div>

As nodes can start a synchronously they may indeed register late. But I’m not totally averse to making it a warning.