# Catch node not finding error

**URL:** <https://discourse.nodered.org/t/catch-node-not-finding-error/20015>\
**Category:** General\
**Created:** [7 January 2020 15:50 UTC](https://discourse.nodered.org/t/catch-node-not-finding-error/20015 "2020-01-07T15:50:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [7 January 2020 16:21 UTC](https://discourse.nodered.org/t/catch-node-not-finding-error/20015/4 "2020-01-07T16:21:52Z")

</div>

Hi @Dave

the Catch node is only able to catch errors that have been logged in a particular way by the node.

Assuming you are using `node-red-contrib-i2c`, you can see how it logs errors in the file here: [https://github.com/nielsnl68/node-red-contrib-i2c/blob/master/i2c/26-i2c.js](https://github.com/nielsnl68/node-red-contrib-i2c/blob/master/i2c/26-i2c.js)

If you search for `node.error` in that file you will see in some places the node calls it with one argument, and in some cases with two. The Catch node will only handle the calls to `node.error()` with two arguments - as the second argument is the message object for the Catch node.

Without a fix to the node, you won't be able to handle those errors in your flow.

---

_[View the full topic](https://discourse.nodered.org/t/catch-node-not-finding-error/20015)._