# More error detection problems

**URL:** <https://discourse.nodered.org/t/more-error-detection-problems/16170>\
**Category:** General\
**Created:** [1 October 2019 20:54 UTC](https://discourse.nodered.org/t/more-error-detection-problems/16170 "2019-10-01T20:54:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [1 October 2019 20:54 UTC](https://discourse.nodered.org/t/more-error-detection-problems/16170/1 "2019-10-01T20:54:04Z")

</div>

In my flows, when an error is detected I use the `catch` node then process the error in the flow.

I move the `msg.error` to `msg.payload` only from habit so I am looking at the payload rather than the error.

I don't see it as a problem.

What is a problem though are the messages I am getting.

This one in particular.

 ![Screenshot%20from%202019-10-02%2006-45-52](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/3/3bcf6686f1195724bcb5751b76da6362b1082aeb.png)

It tells me the `source.id` is 9edd7e2f.abb3a. (I hope I typed it correctly)  
Yet when I search for it, I am told it doesn't exist.

I am suspicious it could be something to do with the `subflow`(s) I am using, but not sure.

If so: There is a problem. Because though that node may be in a subflow, the error detector should at least be able to work this out and either tell me it is in a subflow - and give me the name - or something else to help me find the problem.  
Rather than giving me a _fake_ 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:** [1 October 2019 21:04 UTC](https://discourse.nodered.org/t/more-error-detection-problems/16170/2 "2019-10-01T21:04:27Z")

</div>

You are right this is due to the fact the node reporting the issue is inside a subflow. You are right it could do something more useful to help you identify where it has come from. But it doesn't today. Sorry. Something for a future release to address.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [2 October 2019 06:15 UTC](https://discourse.nodered.org/t/more-error-detection-problems/16170/3 "2019-10-02T06:15:56Z")

</div>

Thanks Nick. I just wanted to be sure of that theory.

No big.