# Fresh NodeRED instance is waiting for a non-existent type to be registered

**URL:** https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027
**Category:** Developing Nodes
**Created:** [21 September 2022 11:27 UTC](https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027 "2022-09-21T11:27:53Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jackcarey](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jackcarey/32/61101_2.png) [@jackcarey](https://discourse.nodered.org/u/jackcarey)
#### Post date: [21 September 2022 11:27 UTC](https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027/1 "2022-09-21T11:27:53Z")

</div>

I am using NodeRED as an [embedded package](https://nodered.org/docs/user-guide/runtime/embedding) on a Windows machine.

I'm trying to create a custom node and I ran into a problem with it not being registered. I thought I'd start again in a new NodeJS project in a new folder and copy the embedding example `index.js` there. When I try to start this fresh server I am still seeing the same message

> Waiting for missing types to be registered:
> 
> - my-custom-node

This server has nothing in it but the example `index.js` file so there are no dependencies and the message still appears even after a reboot. Is NodeRED doing some sort of caching outside of the project folder on my machine? It looks like can't run any NodeRED servers without getting past this, so how can I fix it?

---

<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: [21 September 2022 11:46 UTC](https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027/2 "2022-09-21T11:46:05Z")

</div>

A message like that means the flows file Node-RED is loading contains an instance of `my-custom-node`.

The startup log includes the full path of the flows file it is using - check that is what you expect it to be and what it contains.

---

<div class="post-metadata">

### Author: ![jackcarey](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jackcarey/32/61101_2.png) [@jackcarey](https://discourse.nodered.org/u/jackcarey)
#### Post date: [21 September 2022 12:20 UTC](https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027/3 "2022-09-21T12:20:38Z")

</div>

Thanks, this did the trick. I deleted the flows.json file and restarted the server so it works now.

---

<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: [5 October 2022 12:21 UTC](https://discourse.nodered.org/t/fresh-nodered-instance-is-waiting-for-a-non-existent-type-to-be-registered/68027/4 "2022-10-05T12:21:35Z")

</div>

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