From 312e072070bd2500559fd23d44b0d05ccb188462 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Tue, 18 Aug 2026 05:19:31 -0400 Subject: [PATCH] docs(proto): spell out the monitor-restart clearing emission on AlarmSnapshotStatus --- .../Generated/MxaccessGateway.cs | 5 ++++- .../Protos/mxaccess_gateway.proto | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/src/ZB.MOM.WW.MxGateway.Contracts/Generated/MxaccessGateway.cs b/src/ZB.MOM.WW.MxGateway.Contracts/Generated/MxaccessGateway.cs index 2979802..d171283 100644 --- a/src/ZB.MOM.WW.MxGateway.Contracts/Generated/MxaccessGateway.cs +++ b/src/ZB.MOM.WW.MxGateway.Contracts/Generated/MxaccessGateway.cs @@ -29318,7 +29318,10 @@ namespace ZB.MOM.WW.MxGateway.Contracts.Proto { /// Feed-level snapshot-completeness status. Emitted once on StreamAlarms open /// (after the initial provider_status frame, before the cached active_alarm /// frames) so late joiners learn the current verdict, and again on every change - /// of the truncation verdict observed at reconcile. Mirrors the per-record + /// of the truncation verdict — when a reconcile reports a different verdict, and + /// when the gateway's alarm monitor restarts and drops a truncated verdict with + /// the cache generation it described (feed subscribers outlive that monitor + /// session, so they are sent the clearing frame). Mirrors the per-record /// ActiveAlarmSnapshot.from_truncated_snapshot caveat at feed level so live /// consumers can reason about completeness without polling QueryActiveAlarms. /// diff --git a/src/ZB.MOM.WW.MxGateway.Contracts/Protos/mxaccess_gateway.proto b/src/ZB.MOM.WW.MxGateway.Contracts/Protos/mxaccess_gateway.proto index 85d13a7..b5e2a6b 100644 --- a/src/ZB.MOM.WW.MxGateway.Contracts/Protos/mxaccess_gateway.proto +++ b/src/ZB.MOM.WW.MxGateway.Contracts/Protos/mxaccess_gateway.proto @@ -1035,7 +1035,10 @@ message AlarmProviderStatus { // Feed-level snapshot-completeness status. Emitted once on StreamAlarms open // (after the initial provider_status frame, before the cached active_alarm // frames) so late joiners learn the current verdict, and again on every change -// of the truncation verdict observed at reconcile. Mirrors the per-record +// of the truncation verdict — when a reconcile reports a different verdict, and +// when the gateway's alarm monitor restarts and drops a truncated verdict with +// the cache generation it described (feed subscribers outlive that monitor +// session, so they are sent the clearing frame). Mirrors the per-record // ActiveAlarmSnapshot.from_truncated_snapshot caveat at feed level so live // consumers can reason about completeness without polling QueryActiveAlarms. message AlarmSnapshotStatus {