# Debug node - on/off causing deploy button to get triggered

**URL:** https://discourse.nodered.org/t/debug-node-on-off-causing-deploy-button-to-get-triggered/2221
**Category:** Feature Requests
**Created:** [11 August 2018 08:51 UTC](https://discourse.nodered.org/t/debug-node-on-off-causing-deploy-button-to-get-triggered/2221 "2018-08-11T08:51:28Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [12 August 2018 21:31 UTC](https://discourse.nodered.org/t/debug-node-on-off-causing-deploy-button-to-get-triggered/2221/3 "2018-08-12T21:31:12Z")

</div>

Hi Dave (@dceejay),

I'm pretty sure that a lot of brains were involved in that debate, a long time before I became familiar with Node-Red. However last week there was a related [discussion](https://discourse.nodered.org/t/proposal-allow-the-change-node-to-display-status-objects/1643/12), where @nlecaude posted following request:

> What I'd really like to see in the future is the ability to add a "watchpoint" to a wire in between nodes to allow temporary debugging. What I dislike about debug nodes is they clutter the workspace a lot..

Sometimes I also would like to have a _ **temporary watchpoint** _, without having to deploy my flow. But from your explanation above, I understand that it was a well thought-out decision to remove such functionality from Node-Red. Correct? If so, it could be a nice node-red-contrib-watchpoint. Would appreciate if you could share your experience about such functionality (e.g. pitfalls, ...).

Thanks !!  
Bart

---

_[View the full topic](https://discourse.nodered.org/t/debug-node-on-off-causing-deploy-button-to-get-triggered/2221)._