docs(alarms): note native ack during reconnect is best-effort (integration review)

2026-06-15 15:09:58 -04:00
parent 8899d6e091
commit 7eeb9fb0f5
1 changed files with 7 additions and 0 deletions
@@ -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