# Bug with node-red-contrib-mytimeout?

**URL:** https://discourse.nodered.org/t/bug-with-node-red-contrib-mytimeout/92624
**Category:** General
**Created:** [24 October 2024 07:50 UTC](https://discourse.nodered.org/t/bug-with-node-red-contrib-mytimeout/92624 "2024-10-24T07:50:46Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Sirhc](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@Sirhc](https://discourse.nodered.org/u/Sirhc)
#### Post date: [24 October 2024 07:50 UTC](https://discourse.nodered.org/t/bug-with-node-red-contrib-mytimeout/92624/1 "2024-10-24T07:50:46Z")

</div>

Hello

I am trying to cancel the mytimeout node, by sending payload "cancel" after sending a payload "on".

Instead of cancelling, the timer just resets and starts counting again.

Even if I just send a cancel payload, it starts counting down.

Is this a bug with the node? Can anyone verify that you can cancel the timer?

Link: [node-red-contrib-mytimeout (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-mytimeout)

---

<div class="post-metadata">

### Author: ![Sirhc](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@Sirhc](https://discourse.nodered.org/u/Sirhc)
#### Post date: [24 October 2024 07:57 UTC](https://discourse.nodered.org/t/bug-with-node-red-contrib-mytimeout/92624/2 "2024-10-24T07:57:06Z")

</div>

Never mind - user error! I was using the inject node with " " around the actual payload string, meaning I was sending ""cancel"" instead of "cancel" 🙂 .

---

<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: [7 November 2024 07:57 UTC](https://discourse.nodered.org/t/bug-with-node-red-contrib-mytimeout/92624/3 "2024-11-07T07:57:24Z")

</div>

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