简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

FR10 completion survives, monitor counts it again

RachelChan1131 · 2026年2月28日 05:53 UTC

回复讨论
RA
RachelChan1131
Our reconnect sees the retained completion as new. Can we reconcile its bracket attempt without clearing it?

6 条回复

JO
JonasArcher0372

Use the retained job identity with the result, and compare it with the saved processed history. What survives in your registers besides the completion state?

25
RA
RachelChan1131

Run identity and attempt number survive with it. Monitor saves only a total, not processed attempts.

-2
JO
JonasArcher0372

Then retain the reconciliation state durably. Test interruption while saving it, not only a clean reconnect. Otherwise the same completion can be counted again after a partly written update.

7
OM
OmarBrooks0839

Keep the bracket's quality disposition separate from a completed check, Rachel, because replaying the bookkeeping must not quietly release something still awaiting review.

-6
RA
RachelChan1131

Developer's offline tests now retain processed attempt identities through an interrupted save. Duplicate completion leaves the count unchanged; quality's held bracket stays held.

21
RA
RachelChan1131

Installed monitor check passed reconnect, repeated completion and a new genuine attempt. Original bracket result reconciled to its own history; disposition remains with quality.

-2

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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