# Find failing node

**URL:** <https://discourse.nodered.org/t/find-failing-node/72046>\
**Category:** General\
**Created:** [11 December 2022 17:50 UTC](https://discourse.nodered.org/t/find-failing-node/72046 "2022-12-11T17:50:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulhollands](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paulhollands/32/66071_2.png) [@paulhollands](https://discourse.nodered.org/u/paulhollands)\
**Post date:** [11 December 2022 17:50 UTC](https://discourse.nodered.org/t/find-failing-node/72046/1 "2022-12-11T17:50:48Z")

</div>

Hi,

I'm getting the following error within my NodeRed container logs. I run use NodeRed within Home Assistant and I can't seem to fathom how I go about finding which one of my many nodes is Node 17. Could someone please suggest an approach/ideas. Many thanks

(node:17) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see [Command-line API | Node.js v19.2.0 Documentation](https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode)). (rejection id: 10875)  
(node:17) UnhandledPromiseRejectionWarning: Error: The string could not be parsed by timestring  
at parseTimestring (/data/node\_modules/timestring/index.js:58:11)

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [11 December 2022 18:04 UTC](https://discourse.nodered.org/t/find-failing-node/72046/2 "2022-12-11T18:04:53Z")

</div>

Why not add a `catch` node connected to a `debug` node (set to display the complete msg object) and see if that gives you more. Igf it does, it should show the node ID causing the issue and you can copy that, do a 'find and past that id in and it should hilight that node.

---

<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:** [11 December 2022 18:31 UTC](https://discourse.nodered.org/t/find-failing-node/72046/3 "2022-12-11T18:31:40Z")

</div>

Are you using nodejs 19? 18 is the highest supported version at the moment. That does not mean that the nodejs version 19 is causing the problem, but it is conceivable that it is

---

<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:** [9 February 2023 18:32 UTC](https://discourse.nodered.org/t/find-failing-node/72046/4 "2023-02-09T18:32:30Z")

</div>

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