From b74e139a85708c06474274dedc4321ceec257d93 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Tue, 24 Mar 2026 15:06:42 -0400 Subject: [PATCH] fix(lmxproxy): reset probe timer after reconnect to prevent false stale triggers Without this, the staleness check could fire immediately after reconnect before the first OnDataChange callback arrives, causing a reconnect loop. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../MxAccess/MxAccessClient.Connection.cs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lmxproxy/src/ZB.MOM.WW.LmxProxy.Host/MxAccess/MxAccessClient.Connection.cs b/lmxproxy/src/ZB.MOM.WW.LmxProxy.Host/MxAccess/MxAccessClient.Connection.cs index 3dba659..918ac9c 100644 --- a/lmxproxy/src/ZB.MOM.WW.LmxProxy.Host/MxAccess/MxAccessClient.Connection.cs +++ b/lmxproxy/src/ZB.MOM.WW.LmxProxy.Host/MxAccess/MxAccessClient.Connection.cs @@ -243,6 +243,9 @@ namespace ZB.MOM.WW.LmxProxy.Host.MxAccess if (!IsConnected) { await AttemptReconnectAsync(ct); + // Reset probe timer so the next check gives the new connection + // a full interval to deliver its first OnDataChange callback + _lastProbeValueTime = DateTime.UtcNow; continue; } @@ -267,6 +270,7 @@ namespace ZB.MOM.WW.LmxProxy.Host.MxAccess } await AttemptReconnectAsync(ct); + _lastProbeValueTime = DateTime.UtcNow; } }