Clarify Galaxy native acknowledgement outcome documentation #708

Merged
dohertj2 merged 1 commits from docs/galaxy-ack-rationale into master 2026-10-13 09:10:22 -04:00
Owner

Alarm documentation incorrectly described native acknowledgement as mirroring a Galaxy value-write outcome limitation. The current text now distinguishes the awaited correlated Galaxy ack RPC from the actor route, which logs failures without returning them to the OPC UA client. Galaxy value writes use a separate correlated outcome path. The historical design carries a dated clarification.

Documentation only: source routing and status behavior are unchanged. Verified against GatewayGalaxyAlarmAcknowledger and DriverInstanceActor; independent scope review and diff check passed. No test/build needed for this factual correction. References #614; it remains open for H6 AVEVA event-history acknowledgement and multi-platform parity evidence.

Alarm documentation incorrectly described native acknowledgement as mirroring a Galaxy value-write outcome limitation. The current text now distinguishes the awaited correlated Galaxy ack RPC from the actor route, which logs failures without returning them to the OPC UA client. Galaxy value writes use a separate correlated outcome path. The historical design carries a dated clarification. Documentation only: source routing and status behavior are unchanged. Verified against GatewayGalaxyAlarmAcknowledger and DriverInstanceActor; independent scope review and diff check passed. No test/build needed for this factual correction. References #614; it remains open for H6 AVEVA event-history acknowledgement and multi-platform parity evidence.
dohertj2 added 1 commit 2026-10-13 09:09:53 -04:00
docs(galaxy): clarify native alarm acknowledgement outcomes
v2-ci / build (pull_request) Successful in 7m16s
v2-ci / unit-tests (pull_request) Failing after 3h13m50s
f794dc50b6
dohertj2 merged commit 495606b9fb into master 2026-10-13 09:10:22 -04:00
Sign in to join this conversation.