From 7eeb9fb0f5436071cddcbad0f3f9c81a5bd50afe Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Mon, 15 Jun 2026 15:09:58 -0400 Subject: [PATCH] docs(alarms): note native ack during reconnect is best-effort (integration review) --- docs/AlarmTracking.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/AlarmTracking.md b/docs/AlarmTracking.md index a0bc1588..ca550a82 100644 --- a/docs/AlarmTracking.md +++ b/docs/AlarmTracking.md @@ -113,6 +113,13 @@ Only the **Acknowledge** is routed to the driver. `Confirm` / `AddComment` / `Shelve` operations on a native condition stay on the scripted `AlarmCommandRouter` path (Phase 3 scope is Acknowledge → AVEVA only). +> **Best-effort during reconnect.** If a native ack arrives while the owning +> driver is `Connecting`/`Reconnecting` (or on a non-Primary node), it is +> dropped with a debug log and **not** retried upstream — the OPC UA Part 9 +> `AlarmConditionState` was already committed locally at step 1, so the rare +> outcome is "acked locally but not propagated to AVEVA." Re-issue the ack once +> the driver is reconnected if upstream propagation is required. + ### Legacy sub-attribute path `DriverNodeManager` picks the acknowledger when registering each