"Interval of action" request for improvement
Hello,
I would like to revive an old request to revisit/improve the "interval of action" functionality when configuring rules in NX Witness. After finding related topics here: https://support.networkoptix.com/hc/en-us/community/posts/1500000634881-Push-notifications-Delayed-2nd-notification and here: https://support.networkoptix.com/hc/en-us/community/posts/9849779707031-About-the-behavior-of-Interval-of-action it seems like I am not alone in having the desire to only have an action execute "no more than once per" interval instead of the current functionality where you would receive a notification (or action executed) at least once during the interval as well as AGAIN at the end of the interval (in the case of multiple triggers during the interval).
Although I still find it hard to be able to justify a use-case where you would want/need to ALSO receive a notification (or action executed) at the end of the interval it is clear to me that everyone else who has commented and up-voted on the related topics all agree that there should either be a configuration to modify this behavior or just fix the behavior altogether.
Is there any update on whether this fix/enhancement has been prioritized or is in the works yet? If not, is there a way that we can submit this request and have it voted on as I know there are many who are interested in it being addressed.
Thank you,
-
Official comment
Hello! Thank you for your feedback!
We do have plans to improve the behavior of this feature. While aggregation can be useful in certain scenarios (such as emailing or notifications), we share the perspective that aggregation and throttling should be treated as separate options.
Although we cannot provide a specific timeline at this moment, we're certainly prioritizing this improvement based on the feedback we’ve received and will aim to deliver it as soon as possible.
Thank you for your understanding and support!
-
This is great to hear that it is at least being prioritized now! Please keep us posted with any updated developments and/or timelines.
Thank you,
0 -
Adding my support for this feature request.
We have several remote sites where intrusion detection is used, but repeated triggers within a short time frame are expected — for example, during weekly maintenance visits where staff may move back and forth past a camera for extended periods. In these cases, we only want one notification when motion is first detected, and ideally suppress further notifications for a defined window (e.g., 1 hour).
Another use case is along a remote walking track that tour groups pass through. Stragglers in the group often trigger additional alerts minutes after the initial detection. Being able to suppress notifications for a short duration (e.g., 2–5 minutes) after the first would significantly reduce noise and false alarms.
The current “Interval of action” sends another alert exactly after the configured interval — which isn’t ideal for our needs. Other VMS platforms (like Milestone) provide a “time between emails” setting that works as intended in these scenarios.
Would really appreciate seeing this behavior improved in future updates!
0 -
Is there an update on this feature as this ha annoyingly stopped us progressing with a project.
0 -
This phenomena has caused ongoing trouble for us and I would also like to throw my support behind getting this resolved. We have no use for being notified once and then again a short time later about what happened already, and it makes the user think the camera is giving false alarms when the camera isn't doing anything wrong. Please fix as soon as possible.
0
Please sign in to leave a comment.
Comments
5 comments