docs(historian): clarify modified-value history is infra-gated (no backend modified-read path)

2026-06-15 05:15:50 -04:00
parent bea0b482d4
commit aa1e21f53c
1 changed files with 6 additions and 1 deletions
@@ -163,7 +163,12 @@ data.
  read and there is no "full page ⇒ maybe more" signal to page on. Returning the full result with
  no continuation point is spec-conformant.
 - **No modified-value history** (`HistoryReadModified`). Requests for modified values return
-  `BadHistoryOperationUnsupported`. This is a follow-up.
+  `BadHistoryOperationUnsupported`. This is **infra-gated, not a server-code gap**: the AVEVA
+  Wonderware historian backend (`IHistorianDataSource`, the TCP sidecar client) exposes only a
+  current-value read path — there is no modified/edited-history surface to source the data from. The
+  server-side override is in place (it cleanly rejects modified reads per node) and `IsReadModified`
+  is honoured; serving real modified-value history is unblocked only once the historian client/sidecar
+  grows a modified-read RPC. Until then, rejecting is the correct, spec-conformant behaviour.

 ### Redundancy and authorization