Reconnecting our UR5e monitor gives the same bracket another completion

RachelBennett0783 · 2026年6月25日 00:39 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

RA
RachelBennett0783
The retained completion was high before disconnect, but reconnect counts it again. What should link it to its original job?

3 条回复

NI
NinaChen1197

Compare the retained result's attempt identity with durable processed history, including what survives the monitor and producer restarting. A high level alone cannot tell you it is a new completion. Keep unassignable results for review rather than clearing them or sending the work again.

14分
RA
RachelBennett0783

There is a saved job reference, but our processed set lives only in memory. Closing the monitor loses it.

12分
NI
NinaChen1197

That is one concrete persistence gap. Check the reference's lifetime and reuse rules with controls before using it as a permanent key, then test repeated delivery and reopening against the stored history and displayed count. Moving the set to disk alone does not prove every result identity is unique.

7分

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 和 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。