# DEBUG node in flow when toggle Activation will also trigger DEPLOY why?

**URL:** <https://discourse.nodered.org/t/debug-node-in-flow-when-toggle-activation-will-also-trigger-deploy-why/95259>\
**Category:** General\
**Tags:** docker, debug\
**Created:** [9 February 2025 16:02 UTC](https://discourse.nodered.org/t/debug-node-in-flow-when-toggle-activation-will-also-trigger-deploy-why/95259 "2025-02-09T16:02:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [9 February 2025 16:23 UTC](https://discourse.nodered.org/t/debug-node-in-flow-when-toggle-activation-will-also-trigger-deploy-why/95259/3 "2025-02-09T16:23:59Z")

</div>

> [@Steve-Mcl](#):
>
> There was a recent conversation around this (will try to find link)

Here you go

> [@Should debug nodes be capable of passing the message forwards?](https://discourse.nodered.org/t/should-debug-nodes-be-capable-of-passing-the-message-forwards/95044/47):
>
> TBH, I really dislike that we have to deploy after toggling a button (especially the debug node). Dont get me wrong, i understand why it is the way it is but there are ways we could solve this. For example, a local store (of overrides) that can be updated without deploy would make the situation a lot smoother (storage on systems permitting) but I'm not trying to solve that here and now.

---

_[View the full topic](https://discourse.nodered.org/t/debug-node-in-flow-when-toggle-activation-will-also-trigger-deploy-why/95259)._