# Trigger node seems to lack a time- or iteration-based way to stop sending events

**URL:** <https://discourse.nodered.org/t/trigger-node-seems-to-lack-a-time-or-iteration-based-way-to-stop-sending-events/64033>\
**Category:** General\
**Tags:** function-node\
**Created:** [16 June 2022 21:32 UTC](https://discourse.nodered.org/t/trigger-node-seems-to-lack-a-time-or-iteration-based-way-to-stop-sending-events/64033 "2022-06-16T21:32:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dancook](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dancook/32/63331_2.png) [@dancook](https://discourse.nodered.org/u/dancook)\
**Post date:** [16 June 2022 21:32 UTC](https://discourse.nodered.org/t/trigger-node-seems-to-lack-a-time-or-iteration-based-way-to-stop-sending-events/64033/1 "2022-06-16T21:32:48Z")

</div>

I've been trying to replace looptimer and stoptimer nodes (due to the apparent deprecation of them). Mostly I am using a trigger node in this effort. But what seems fundamentally missing is a way for the trigger node to stop sending events after a set length of time or a set # of event instances. Am I just missing something which is right in front of me?

---

<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:** [15 August 2022 21:33 UTC](https://discourse.nodered.org/t/trigger-node-seems-to-lack-a-time-or-iteration-based-way-to-stop-sending-events/64033/2 "2022-08-15T21:33:21Z")

</div>

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