# Add a way to reset the new debug node counter (v3 feature) via a msg property

**URL:** <https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270>\
**Category:** Feature Requests\
**Created:** [6 May 2022 07:48 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270 "2022-05-06T07:48:49Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rapejim](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rapejim/32/61162_2.png) [@Rapejim](https://discourse.nodered.org/u/Rapejim)\
**Post date:** [6 May 2022 07:48 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/1 "2022-05-06T07:48:49Z")

</div>

The new feature (message counter as status) of debug node in 3.0.0 beta 1 is awesome but we can't reset it to 0.

Maybe with a "msg.reset" input like at delay node or join node... 😜

Thanks!!

---

<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:** [6 May 2022 07:54 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/2 "2022-05-06T07:54:55Z")

</div>

I second this FR 🙂

I would personally avoid `msg.reset` as it may get caught with a `msg.reset` intended for another node?  
e.g. `msg.debugCountReset` or `msg.countReset` might be better ?

Open to debate of course.

---

<div class="post-metadata">

**Author:** ![Rapejim](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rapejim/32/61162_2.png) [@Rapejim](https://discourse.nodered.org/u/Rapejim)\
**Post date:** [6 May 2022 08:10 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/3 "2022-05-06T08:10:12Z")

</div>

> [@Steve-Mcl](#):
>
> I would personally avoid `msg.reset` as it may get caught with a `msg.reset` intended for another node?  
> e.g. `msg.debugCountReset` or `msg.countReset` might be better ?

And a simple word like `msg.clear`? 🤔

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [6 May 2022 08:24 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/4 "2022-05-06T08:24:31Z")

</div>

I'd like to see the status message appear after the counter - best of both worlds!

---

<div class="post-metadata">

**Author:** ![Rapejim](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rapejim/32/61162_2.png) [@Rapejim](https://discourse.nodered.org/u/Rapejim)\
**Post date:** [6 May 2022 09:30 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/5 "2022-05-06T09:30:51Z")

</div>

> [@zenofmud](#):
>
> I'd like to see the status message appear after the counter - best of both worlds!

Maybe if the "message count" would a independent checkbox, we could combinate it with a custom status.

---

<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:** [6 May 2022 09:34 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/6 "2022-05-06T09:34:39Z")

</div>

I'm thinking that maybe a case for the use of an underscore e.g. msg.\_reset (or even double underscore) to indicate some sort of private message only intended for the debug node

Just throwing it in for discussion

> [@Rapejim](#):
>
> And a simple word like `msg.clear`

Has same issue as using msg.reset - could end up in a namespace type conflict

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 May 2022 10:19 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/7 "2022-05-06T10:19:17Z")

</div>

rather than a msg I would say the click to pause output button should pause the count, and then also clear the count when you re-enable.

(and no to combining with status words as you then get into should it be before words or after words and next it will be variable substitution and ... 🙂 )

---

<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:** [6 May 2022 10:42 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/8 "2022-05-06T10:42:59Z")

</div>

> [@dceejay](#):
>
> rather than a msg I would say the click to pause output button should pause the count, and then also clear the count when you re-enable.

This was all discussed at great length in the original issue/PR.

I think using the button doesn't give the flexibility needed - it is a manual reset. If you wanted to have a 'count of messages since some event happened', you'd want to be able to programmatically reset it in the flow.

Without [bike-shedding](https://thedecisionlab.com/biases/bikeshedding) it too much, we can add support for `msg.resetCount` - succinct, to the point, and not going to clash with existing use of `msg.reset`.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 May 2022 11:33 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/9 "2022-05-06T11:33:54Z")

</div>

... but it's Friday... and I like bikes.... and sheds... 😇

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 May 2022 12:04 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/10 "2022-05-06T12:04:05Z")

</div>

But I've never really liked the combination. Maybe due to the school trauma of having my bike lock stolen but the bike left behind! 🤣

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [6 May 2022 12:17 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/11 "2022-05-06T12:17:38Z")

</div>

I must be living in a sheltered world as I'd never heard of 'bike-shedding' before today. 🚴‍♀️ 🚴‍♂️

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 May 2022 12:28 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/12 "2022-05-06T12:28:08Z")

</div>

Well as long as it's not related to tractor sheds we may be ok... (but I'm not going to search google just in case...!!!)

---

<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:** [5 July 2022 12:28 UTC](https://discourse.nodered.org/t/add-a-way-to-reset-the-new-debug-node-counter-v3-feature-via-a-msg-property/62270/13 "2022-07-05T12:28:35Z")

</div>

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