# CATCH node control to turn it on / off

**URL:** <https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509>\
**Category:** Feature Requests\
**Created:** [13 September 2019 13:31 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509 "2019-09-13T13:31:45Z")\
**Posts on this page:** 9\
**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:** [13 September 2019 13:31 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/1 "2019-09-13T13:31:45Z")

</div>

For error catching it is handy so any errors can be caught and sent back to a place for handling.

But if you are working on the flow it is sometimes annoying having the errors _caught_ and not seeing them as if the `CATCH` nodes wasn't there.

It would (could?) be nice if while you are working on that flow that you could _disable_ the node.  
So if there is an error it isn't _hidden_. It is easily visible in the `debug` window to the right of the screen.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [13 September 2019 14:22 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/2 "2019-09-13T14:22:57Z")

</div>

In V1.0, you can disable any node (button at bottom of node config) so this is already been implemented

FTAOD I wouldn't recommend upgrading a installation to 1.0 beta until ALL bugs have been eliminated from it 🙂  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/9/90def58f6ae05109411e9ad280ccd1b4b7f95d2d.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/d991c18283817d617f839c5a84adcbe3de8b36d8.png)

---

<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:** [13 September 2019 21:28 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/3 "2019-09-13T21:28:09Z")

</div>

> [@cymplecy](#):
>
> FTAOD

Nearly got it. I kind kind of resolve the meaning, but for the sake of getting it right......

For The Act Of Doing?  
Doesn't quite sound right.

But yeah, thanks.

I am really holding off the update.  
Though I feel I should on at least one machine to help find any bugs.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [14 September 2019 08:28 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/4 "2019-09-14T08:28:36Z")

</div>

> [@Trying\_to\_learn](#):
>
> Though I feel I should on at least one machine to help find any bugs.

noooooooooooooooooooooooooooooooooooo............................. 🙂

Unless you've got one that definitely works 100% all of the time and has been stable for a while - if you have one of them then that would be a candidate to test out

---

<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:** [14 September 2019 08:30 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/5 "2019-09-14T08:30:56Z")

</div>

What,

Seriously... ?

Haven't I found a few?

I would probably put it on a VM though.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [14 September 2019 08:31 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/6 "2019-09-14T08:31:53Z")

</div>

I edited my post 🙂

---

<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:** [14 September 2019 08:32 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/7 "2019-09-14T08:32:59Z")

</div>

No worries.

I have a couple of VM's I could put it on one.

Then have a big play with bug finding.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [14 September 2019 08:33 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/8 "2019-09-14T08:33:05Z")

</div>

> [@Trying\_to\_learn](#):
>
> I would probably put it on a VM though.

Moving it to a VM would negate the requirement that its been working for a while - you'd be introducing a new variable into the equation 🙂

---

<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:** [14 September 2019 08:34 UTC](https://discourse.nodered.org/t/catch-node-control-to-turn-it-on-off/15509/9 "2019-09-14T08:34:05Z")

</div>

Oh.

Drats.

Thanks.