Our reconnect sees the retained completion as new. Can we reconcile its bracket attempt without clearing it?
FR10 completion survives, monitor counts it again
RachelChan1131 · 28 Feb 2026, 05:53 UTC
6 replies
Replying to RachelChan1131
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?
25pointsReplying to JonasArcher0372
Run identity and attempt number survive with it. Monitor saves only a total, not processed attempts.
-2pointsReplying to RachelChan1131
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.
7pointsReplying to RachelChan1131
Keep the bracket's quality disposition separate from a completed check, Rachel, because replaying the bookkeeping must not quietly release something still awaiting review.
-6pointsReplying to JonasArcher0372
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.
21pointsReplying to 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.
-2pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .