Galaxy: with ReplayOnSessionLost=false a reconnect leaves every subscription silently dead (last Good values, health Healthy) #862

New Issue

2026-11-11T10:51:51-05:00

dohertj2 commented

2026-11-11 10:51:51 -05:00

From the #859/#861 reviews. After a gateway session is recreated with ReplayOnSessionLost=false, the driver keeps its subscriptions but never re-advises them (a recreated gateway session carries no subscriptions over), health returns to Healthy, and every subscribed node keeps its last value with Good quality. The only signal is a log line (raised to Warning in the #859 work). Surface it: publish BadNoCommunication for the stranded subscriptions and/or report the driver Degraded until they are re-subscribed, or reconsider whether false should be a supported setting at all.

From the #859/#861 reviews. After a gateway session is recreated with `ReplayOnSessionLost=false`, the driver keeps its subscriptions but never re-advises them (a recreated gateway session carries no subscriptions over), health returns to Healthy, and every subscribed node keeps its last value with Good quality. The only signal is a log line (raised to Warning in the #859 work). Surface it: publish `BadNoCommunication` for the stranded subscriptions and/or report the driver Degraded until they are re-subscribed, or reconsider whether `false` should be a supported setting at all.

dohertj2 added the type:followup priority:p3 labels 2026-11-11 10:51:51 -05:00

dohertj2 referenced this issue from a commit

2026-11-11 11:28:50 -05:00

fix(galaxy): stranded subscriptions after a no-replay reconnect go Bad + Degraded (#862)

dohertj2 referenced this issue from a commit

2026-11-11 11:28:50 -05:00

Merge #862 Galaxy: reconnect with ReplayOnSessionLost=false publishes BadNoCommunication for stranded subscriptions and reports Degraded

dohertj2 commented

2026-11-11 11:28:51 -05:00

Fixed (33e10c22). Pushed to master in e857135e. With ReplayOnSessionLost=false, a reconnect now publishes BadNoCommunication for every tag of every stranded subscription and GetHealth() reports Degraded (message names the setting and count) until the last stranded subscription is unsubscribed or the runtime is torn down; new subscriptions after the reconnect work normally. Note: the comms-loss watchdog re-initializes a Degraded driver with no data after 90 s, which re-subscribes everything (effectively a delayed replay); per-platform probes still go stale with replay off. Documented in docs/drivers/Galaxy.md.

Fixed (`33e10c22`). Pushed to master in `e857135e`. With `ReplayOnSessionLost=false`, a reconnect now publishes `BadNoCommunication` for every tag of every stranded subscription and `GetHealth()` reports Degraded (message names the setting and count) until the last stranded subscription is unsubscribed or the runtime is torn down; new subscriptions after the reconnect work normally. Note: the comms-loss watchdog re-initializes a Degraded driver with no data after 90 s, which re-subscribes everything (effectively a delayed replay); per-platform probes still go stale with replay off. Documented in docs/drivers/Galaxy.md.

dohertj2 closed this issue

2026-11-11 11:28:51 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#862