• Date
    Luke42151
  • Date
  • Replies 3 replies
  • Subscribers 110 subscribers
  • Views 2267 views
  • Users 0 members are here

Conductor - sending SMS and Email Alerts non stop until error rectified

Hi,

Does anyone else have this problem?

I have only noticed this issue with breaker/RCD trips on sensor 3 racks with CEM3s.

What is happening is, The Net3 Conductor will constantly send sms and emails reporting the tripped breaker, until i rectify the error.

On one occasion i was away from work, a breaker tripped, and i received over 800 emails about it before my email address decided to block it. The time stamp on the emails was all immediately, one after another. Its not like the email alert was once ever 10mins, it was less than every second.

I decided to remove the sms alerts because of this same issue.

Any ideas?

Parents

  • It sounds like the alert system may be triggering repeatedly instead of applying a cooldown or alert-suppression rule after the first breaker/RCD event. Sending hundreds of emails or SMS messages for the same fault can quickly overwhelm the notification channel.

    A reliable SMS API Solution can help when combined with event-based alert logic, rate limiting, duplicate detection, and configurable retry intervals. Ideally, the system should send the initial alert, suppress repeated notifications for the same event, and send another message only when the fault is cleared or a defined interval has passed.

    Checking the Net3 Conductor event configuration, notification retry settings, and duplicate-alert handling would be a good place to start.

Reply

  • It sounds like the alert system may be triggering repeatedly instead of applying a cooldown or alert-suppression rule after the first breaker/RCD event. Sending hundreds of emails or SMS messages for the same fault can quickly overwhelm the notification channel.

    A reliable SMS API Solution can help when combined with event-based alert logic, rate limiting, duplicate detection, and configurable retry intervals. Ideally, the system should send the initial alert, suppress repeated notifications for the same event, and send another message only when the fault is cleared or a defined interval has passed.

    Checking the Net3 Conductor event configuration, notification retry settings, and duplicate-alert handling would be a good place to start.

Children
No Data
Related

www.etcconnect.com