Throttle Step in @novu/framework
Are you planning to bring the throttle step to SDK?
Context: I have a workflow that sends alarms if a temperature sensor goes above some specific value. In some cases the temperature is right on the limit and it triggers the alarms multiple times. I want group and throttle the alarms by
sensorId-alarmCodeThrottle Step | Novu Documentation
Learn how to use the Throttle step in Novu workflows to control notification frequency.
2 Replies
Hi Andre
I am checking with the team on support of throttle step in framework
I am checking with the team on support of throttle step in framework
Thank you.
Also, ideally it should be possible to add a throttle step at topic-level.
Why?
From docs: https://novu.co/pricing/
Novu creates one event per topic subscriber after fan-out, this means that a workflow trigger to a topic with 100 subscribers creates 100 eventsThis means that even if I add a throttle step to the workflow (to not bother the customers) I'm still consuming the events without sending any actual notifications. I think that throttle at topic level could solve this issue and reduce drastically the number of produced events. Context: I have a topic with 25 subscribers and my system emits 2 event types for every alarm -
alarm created (e.g, temperature goes above the safe level)
- alarm cleared (e.g, temperature gets back to safe level)
When sensor has some fault it might report inconsistent readings every couple of seconds.
In the scenario above, a single sensor that's "stuck" in the alarm created/alarm cleared loop can easily consume more than a 1000 events in short period of time.Pricing - Novu
Flexible pricing for companies and developers