When our monitor reconnects, a completion signal retained from before the outage can be treated as a new completion. We're tracking sample verification tracking with Universal Robots UR5e in a fixture-checking station under commissioning, using a sample bracket. I'm trying to reconcile the signal with its job, without automatic resubmission or simply clearing the retained state.
The first read after reconnect fools our application (sample verification tracking)
TheoAdams0149 · 2026年5月24日 05:33 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
10 条回复
Does your trace show completion staying high through the outage? And does the application retain what it already consumed?
21分回复 FelixAli0197
It stays high. Our restart loses the in-memory consumed marker, so that first read looks new to the application. Annoyingly simple once it's visible.
13分Replay reconnect offline against a durable job record. Match the retained completion before changing counts; persisting the consumed marker should prevent the repeat.
6分回复 FelixAli0197
Only if that marker identifies the right job. One persisted boolean could hide a genuinely new completion instead
11分You're right about the missing identity condition. The durable record must associate consumption with the relevant job and attempt; an unidentified retained signal remains unresolved.
14分回复 FelixAli0197
@FelixAli0197 Would an explicit reconciliation phase help on reconnect, so the application doesn't treat its initial retained-state read as an ordinary new event?
17分@TheoAdams0149 Yes. Read the retained state, compare it with durable history and decide what it establishes. Reconnecting itself isn't evidence of new completion.
7分回复 FelixAli0197
My own application reset its last-seen state through a shared startup path, so its edge detector treated the initial high value as an observed transition after reconnect.
16分@ImranAllen0305 The duplicate-read mechanism is clear from our trace. A completed fix still depends on persistent, identity-based reconciliation passing the offline reconnect and restart checks.
21分That explains the duplicate without overclaiming the fix. Identity and restart verification are sensible completion conditions.
16分