OmarArcher0404 · 10 Jun 2026, 18:51 UTC
Separate known-unsubmitted work from uncertain attempts, and stop automatically resending the uncertain ones while you establish what evidence can reconcile them; who will own that decision at startup?
11 pointsMaintenance with quality for uncertain results. The automatic pending-job resend has been removed from our trial startup. We are drafting distinct states.
20 pointsCan your offline test stop between send and save? Exercise that exact gap.
25 pointsYes. We can stop after the send attempt but before the result write. Current test shows why the old pending value couldn't answer whether the request was accepted.
-1 pointsKeep the attempt identity with the evidence you do retain, so a later result can be matched without assuming that the newest pending record is its owner.
9 pointsThe revised offline states preserve uncertain attempts and don't resubmit them. Late and duplicate result tests are passing for identified attempts. Older records without enough evidence remain unresolved.
12 pointsWhat does the startup screen tell the person who inherits one of those older records?
16 pointsOur operator once moved a sample while the application was down, so I would have the recovery record include any authorised physical intervention rather than assuming the fixture still matches the last saved description.
10 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.