Content
Investigated the delayed callout response for the Influent Pumps UPS Trip
alarm (UPS_0112_ON_BACKUP_Alm_TgtDisagree) that activated at 03:45:55 on
4/20/2026 and was not acknowledged until 04:03:37. Review of the WIN-911
logs showed that the alarm condition chattered repeatedly with very short
active durations (5–7 seconds per occurrence) before clearing, and the
assigned callout workflow ("Test 2") was configured to send notifications
only when the alarm was in the Active + Unacknowledged state. Because the
workflow's callout list cycles through contacts at one-minute intervals,
each dispatch attempt evaluated the alarm state at the moment of dispatch —
and since the alarm was inactive (but still unacknowledged) for the
majority of the cycle, WIN-911 correctly skipped notifications to the
District Call Out Phone, Mike Arias, and Mycal Jones contacts on multiple
passes per the configured Send Notification settings. A successful dispatch
eventually occurred to Mycal Jones at 03:54:58 when the workflow cycle
happened to coincide with a brief active window; the call connected on each
of four attempts but failed three times due to invalid authorization code
entry on the receiving end before being acknowledged on the fourth attempt
at 04:03:37. To prevent this filtering behavior from suppressing future
callouts on chattering alarms, the Test 2 workflow's Notifications Behavior
was updated to include both Active + Unacknowledged and Inactive +
Unacknowledged states, ensuring the callout chain proceeds to completion
based on acknowledgment status rather than instantaneous alarm state. It is
additionally recommended that the underlying chatter on the UPS
target/feedback disagreement signal be investigated at the source (PLC
logic or UPS feedback wiring) to address the root cause.
On Tue, Apr 28, 2026 at 9:10 PM Kevin Seifert <kevin@autosysnet.com> wrote:
> @Mason Radke <mason@autosysnet.com>
>
> Please look into this alarm anomaly.
[... earlier replies trimmed ...]
--
-Mason