# How to catch config node error

**URL:** https://discourse.nodered.org/t/how-to-catch-config-node-error/52573
**Category:** General
**Created:** [22 October 2021 13:16 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573 "2021-10-22T13:16:03Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [22 October 2021 13:16 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/1 "2021-10-22T13:16:03Z")

</div>

Hi all,  
I'm using the library node-red-contrib-s7 that have a config node where is stored the configuration of the comunication.  
I need to catch this error that derive from the config node  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/7/774dc25ffe76945ef946ef8c4433c775a22d8ad5.png)  
If I catch the error in this way it don't works

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/2/7223ce04b7c44452e1b40e7e0a123209a1680e24.png)

there is a method to catch this error?

---

<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: [22 October 2021 14:03 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/2 "2021-10-22T14:03:03Z")

</div>

Does it appear if you connect a debug node to the S7 node? Set it to output complete message in case it is not in the payload.

---

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [22 October 2021 15:33 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/3 "2021-10-22T15:33:09Z")

</div>

The debug node is alredy set to complete message object.  
I think this error is generated by the node s7endpoint and not by the s7 in node  
This is the library to be more exhaustive.  
[node-red-contrib-s7](https://flows.nodered.org/node/node-red-contrib-s7)

---

<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: [22 October 2021 15:43 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/4 "2021-10-22T15:43:01Z")

</div>

You haven't got a debug node connected to the S7 node, it is connected to the Catch node.  
Errors in the config node may be propagated up to the visible node.

---

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [22 October 2021 15:55 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/5 "2021-10-22T15:55:17Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/1/81a59e38edee686b6c4507e9a17ec2a23fa64333.png)  
Do you mean it like this?  
I still don't catch the error

---

<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: [22 October 2021 15:59 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/6 "2021-10-22T15:59:31Z")

</div>

Does it show anything?

---

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [22 October 2021 16:12 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/7 "2021-10-22T16:12:05Z")

</div>

No only the old error (PLC II is the name of s7 endpoint 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: [22 October 2021 16:17 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/8 "2021-10-22T16:17:14Z")

</div>

What old error?

---

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [25 October 2021 07:01 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/9 "2021-10-25T07:01:44Z")

</div>

[![](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/7/774dc25ffe76945ef946ef8c4433c775a22d8ad5.png) ](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/7/774dc25ffe76945ef946ef8c4433c775a22d8ad5.png)  
This only in the debug console

---

<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: [25 October 2021 09:34 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/10 "2021-10-25T09:34:14Z")

</div>

> [@Giu-seppe](#):
>
> node-red-contrib-s7

I notice that there is a [similar issue](https://github.com/st-one-io/node-red-contrib-s7/issues/98) already reported against the node and that this has not been responded to. It may be that the node is no longer supported.

---

<div class="post-metadata">

### Author: ![Giu-seppe](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/giu-seppe/32/40489_2.png) [@Giu-seppe](https://discourse.nodered.org/u/Giu-seppe)
#### Post date: [25 October 2021 12:47 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/11 "2021-10-25T12:47:10Z")

</div>

Ok I understand, so the error generated from this library is not catchable 😕

---

<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: [25 October 2021 13:07 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/12 "2021-10-25T13:07:20Z")

</div>

It is up to the author of the node to pass the error to node-red so that it can be caught by a Catch node. Currently it looks as if it is just logging it.

---

<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: [24 December 2021 13:07 UTC](https://discourse.nodered.org/t/how-to-catch-config-node-error/52573/13 "2021-12-24T13:07:24Z")

</div>

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