# Can't find ID shown in node-red-log

**URL:** <https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660>\
**Category:** General\
**Created:** [24 July 2020 16:22 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660 "2020-07-24T16:22:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [24 July 2020 16:22 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/1 "2020-07-24T16:22:55Z")

</div>

I'm looking at the node-red-log and I am getting the following info...

"[info] [range:a8e61fec.d9baa] Not a number: NaN"

But if I search for that id "a8e61fec.d9baa" it doesn't find anything?

Any ideas?

---

<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 July 2020 16:24 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/2 "2020-07-24T16:24:44Z")

</div>

Most likely a node inside a subflow as they get internally generated IDs when being created in the runtime.

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [24 July 2020 17:50 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/3 "2020-07-24T17:50:51Z")

</div>

I searched inside each of the subflows and still came up empty... so does that mean it is not possible to locate the offending node by ID?

---

<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 July 2020 18:04 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/4 "2020-07-24T18:04:05Z")

</div>

When the runtime creates an instance of a subflow it has to generate new ids for all of the internal nodes so they don't clash with another instance of the same subflow.

With the default level of logging that can make it hard to track down.

But if you enable `trace` level logging you'll get (a lot of) information about all nodes the runtime creates and that will include what generated ids have been assigned to what nodes.

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [24 July 2020 19:11 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/5 "2020-07-24T19:11:34Z")

</div>

Thanks, I'll play with the trace level logging and see if I can get it sorted out.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 July 2020 20:41 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/6 "2020-07-24T20:41:16Z")

</div>

Have you got a lot of Range nodes inside subflows? If you give them all names then the name will appear in the error instead of the id.  
Also, you could add a function node in front of each one checking for NaN and taking appropriate action.

---

<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:** [22 September 2020 20:41 UTC](https://discourse.nodered.org/t/cant-find-id-shown-in-node-red-log/30660/7 "2020-09-22T20:41:22Z")

</div>

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