# Question in debuging a flow - How to stopp node RED in a certain condition?

**URL:** <https://discourse.nodered.org/t/question-in-debuging-a-flow-how-to-stopp-node-red-in-a-certain-condition/57648>\
**Category:** General\
**Tags:** debugging\
**Created:** [2 February 2022 14:13 UTC](https://discourse.nodered.org/t/question-in-debuging-a-flow-how-to-stopp-node-red-in-a-certain-condition/57648 "2022-02-02T14:13:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lostbits](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lostbits/32/43407_2.png) [@lostbits](https://discourse.nodered.org/u/lostbits)\
**Post date:** [2 February 2022 14:13 UTC](https://discourse.nodered.org/t/question-in-debuging-a-flow-how-to-stopp-node-red-in-a-certain-condition/57648/1 "2022-02-02T14:13:41Z")

</div>

Hi,

I have some strange effects in my flow (multiple feedback loops) and i cant find out where the message came from, since there are by far too many messages around and the wrong message content happens one of 1000 messages.  
By wrong content i mean, my flow sees a message, which should not have come from this point ...

But, in a node function I can see the problem - and I react to it. But I like to know, why this happened. If it would be possible to do a Node.STOPP() or something, which stopps the flow completely I could have a look at the log, I am wirting.

Is there a way?

Kind regards,

lotsbits

---

<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:** [2 February 2022 14:22 UTC](https://discourse.nodered.org/t/question-in-debuging-a-flow-how-to-stopp-node-red-in-a-certain-condition/57648/2 "2022-02-02T14:22:31Z")

</div>

Hi @lostbits

Have a look at [GitHub - node-red/node-red-debugger: A flow debugger for Node-RED 2.x](https://github.com/node-red/node-red-debugger) - this is a plugin for Node-RED that adds debugger tools for your flow.

You can set breakpoints on node inputs and outputs that will pause the runtime when a message arrives at it. You can then examine all of the paused messages.

If you are detecting this 'bad' message in a Function node, you could add an extra output to the Function and use `node.send( ... )` to send the message to that new output. That gives you an output to add a breakpoint to.

---

<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:** [16 February 2022 14:22 UTC](https://discourse.nodered.org/t/question-in-debuging-a-flow-how-to-stopp-node-red-in-a-certain-condition/57648/3 "2022-02-16T14:22:43Z")

</div>

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