# Trigger "Resend it every" option to have "Then Send"

**URL:** https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214
**Category:** Feature Requests
**Created:** [15 December 2021 05:18 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214 "2021-12-15T05:18:02Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![step-chew](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/step-chew/32/50079_2.png) [@step-chew](https://discourse.nodered.org/u/step-chew)
#### Post date: [15 December 2021 05:18 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/1 "2021-12-15T05:18:02Z")

</div>

"Then Send" parameter is available for "wait for" option, after the timeout. However, it's not offered for "resend it every" option. It'd be nice if it could be added as well.

**Scenario:**  
I have an event driven reminder, say when I turn on the terrace light, the trigger will be fired (initially fire **nothing** so it doesn't trigger anything), and it "resends" every 30 minutes to send a notification to remind me that the light is still on......until I reset the trigger (msg.reset = true, or such like)

---

<div class="post-metadata">

### Author: ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [15 December 2021 21:20 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/2 "2021-12-15T21:20:51Z")

</div>

Also, the "resend it every" option should have a "for N times (N = 0, no limit)" option, in case you don't want it to go on forever.

---

<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: [15 December 2021 23:12 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/3 "2021-12-15T23:12:42Z")

</div>

Can't this just be done by using two trigger nodes ? One to send nothing then trigger the next set to repeat mode ?  
Likewise @drmibell a 2nd trigger node can be used to reset a repeating one after a longer time interval.

---

<div class="post-metadata">

### Author: ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [15 December 2021 23:46 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/4 "2021-12-15T23:46:26Z")

</div>

> [@dceejay](#):
>
> reset a repeating one after a longer time interval.

Almost what I had in mind, but not exactly. Getting a given number of repeats with a given spacing would require setting each interval properly. Then changing either the number or spacing (keeping the other fixed) would mean changing both intervals. It works, but the independent parameters aren't quite right. I've used contributed nodes like [looptimer](https://flows.nodered.org/node/node-red-contrib-looptimer) and [msg-resend](https://flows.nodered.org/node/node-red-contrib-msg-resend) for this, but it would be nice to have this in a core node.

---

<div class="post-metadata">

### Author: ![step-chew](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/step-chew/32/50079_2.png) [@step-chew](https://discourse.nodered.org/u/step-chew)
#### Post date: [17 December 2021 11:14 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/5 "2021-12-17T11:14:16Z")

</div>

Came across my mind after I posted the feature request - yes but it seems to me more of a "workaround" for now. As @drmibell pointed out, there'll be 2 intervals (2 nodes) to maintain, and both nodes will also have to take in the `msg.reset`, making the nodes to look a bit tangled up.

Especially when I have multiple nodes piping into this trigger node (separated by `msg.topic`), the end result may look a little scary 😅

---

<div class="post-metadata">

### Author: ![step-chew](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/step-chew/32/50079_2.png) [@step-chew](https://discourse.nodered.org/u/step-chew)
#### Post date: [17 January 2022 04:25 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/6 "2022-01-17T04:25:26Z")

</div>

Any luck with the implementation of this feature? Or at least placed in the backlog? I still think it's viable. Otherwise, please enlighten me if there's a better way to achieve what I want to achieve 🙂

---

<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: [17 January 2022 09:22 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/7 "2022-01-17T09:22:05Z")

</div>

The "workaround" is the Node-RED way to do it... build up extended capability by joining nodes together. You can always collapse them into a subflow if you need to.

---

<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: [18 March 2022 09:22 UTC](https://discourse.nodered.org/t/trigger-resend-it-every-option-to-have-then-send/55214/8 "2022-03-18T09:22:08Z")

</div>

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