# Capturing errors caused inside link-call flows

**URL:** <https://discourse.nodered.org/t/capturing-errors-caused-inside-link-call-flows/80010>\
**Category:** General\
**Created:** [22 July 2023 16:10 UTC](https://discourse.nodered.org/t/capturing-errors-caused-inside-link-call-flows/80010 "2023-07-22T16:10:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [22 July 2023 17:46 UTC](https://discourse.nodered.org/t/capturing-errors-caused-inside-link-call-flows/80010/3 "2023-07-22T17:46:49Z")

</div>

Sorry that's not what I want, my goal is this:

 ![Screen Shot 2023-07-22 at 19.42.43](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/8/d8e5ef4a45e3ef58aec4eb185c7570de53bc39d3.png)

I have several link-call nodes chained together and if one of the fails, then the single catch node should capture it. The variation you posted would continue down the flow if an exception happened inside the link-call node.

That works fine if you only have one link-call node 😉

Hence me wondering whether the link-call node could throw/raise/trigger the error of the flow it called if there is an `msg` object returned that contains an `error` attribute.

---

_[View the full topic](https://discourse.nodered.org/t/capturing-errors-caused-inside-link-call-flows/80010)._