Clarify Galaxy native acknowledgement outcome documentation #708
Reference in New Issue
Block a user
Delete Branch "docs/galaxy-ack-rationale"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.