# Catch warnings (yellow errors)

**URL:** <https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991>\
**Category:** General\
**Tags:** debugging, opcua\
**Created:** [13 October 2022 15:31 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991 "2022-10-13T15:31:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![milkbaconleopardveal](https://avatars.discourse-cdn.com/v4/letter/m/919ad9/32.png) [@milkbaconleopardveal](https://discourse.nodered.org/u/milkbaconleopardveal)\
**Post date:** [13 October 2022 15:31 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991/1 "2022-10-13T15:31:57Z")

</div>

Hello there,  
has anyone any idea on how to catch these _warnings_ from the opc-ua Client node?  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/c/2c33f674b2171a225c0484bf733527ea13582c14.png)  
or from any node that puts out warnings.

Kind of like a **Catch** node but for _warnings_. It would be useful to restart the flows when I get a specific error from any node.

Node-Red version: 3.0.2  
Plugin version: node-red-contrib-opcua v0.2.289

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [13 October 2022 15:38 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991/2 "2022-10-13T15:38:31Z")

</div>

Same question here...

> [@Disable debug log for node-red-contrib-opcua](https://discourse.nodered.org/t/disable-debug-log-for-node-red-contrib-opcua/68343/1):
>
> Hello there, I'd like to know if there is a way to disable the verbose logging in the Debug panel generated by the plugin node-red-contrib-opcua as you can see here: It's useful but it prevents me to use the debug panel for debug purposes. Thanks a lot in advance, Fabio

See post #4

---

<div class="post-metadata">

**Author:** ![milkbaconleopardveal](https://avatars.discourse-cdn.com/v4/letter/m/919ad9/32.png) [@milkbaconleopardveal](https://discourse.nodered.org/u/milkbaconleopardveal)\
**Post date:** [13 October 2022 15:42 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991/3 "2022-10-13T15:42:08Z")

</div>

Actually not, I'd like to catch warnings to use them in another flow/node, the question you quote is asking for a removal/disabling of such warning messages.

It's very similar to this one:

> [@How to "catch" node.warn(msg)](https://discourse.nodered.org/t/how-to-catch-node-warn-msg/3738):
>
> I love using the "catch" node to catch all errors from a flow and then pipe them to any notification system like Telegram, Email, etc. Is there anything similar that works with node.warn()? How could I catch .warn() messages and send them on to some notification system?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [13 October 2022 15:45 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991/4 "2022-10-13T15:45:12Z")

</div>

Sure, ok, it was implicit I guess but I was trying to point out that warnings are NOT catchable. (the reason other OP wants to disable them)

Sorry i wasn't clear.

You would have to request to the author that he changes these to errors AND includes the `msg` object in order for them to be catchable.

Alternatively, request that warnings are output on a separate output of the node.

As it stands, it is not possible.

---

<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:** [12 December 2022 15:46 UTC](https://discourse.nodered.org/t/catch-warnings-yellow-errors/68991/5 "2022-12-12T15:46:09Z")

</div>

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