Separate known-unsent work from submitted work with an unknown outcome, and reconcile the latter against an identifiable job record before considering any retry; I would also test the crash around each durable write, because renaming pending does not close the send-and-save gap.
Pending now means two different things in our FR10 startup file
MeiAbbott0081 · 12 Jun 2026, 20:30 UTC
I need to remove automatic resubmission from an ambiguous state. Our application sent a plate-inspection request and crashed before saving the result, but startup treats its pending entry like work never sent. The FR10 may have continued; the local file cannot establish otherwise.
2 replies
Add to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.