Recovering part inspection bookkeeping across a crash (Fairino FR5)

GraceBell0668 · 10 Jul 2026, 00:44 UTC

Reply to discussion
GR
GraceBell0668
Our application crashed after sending a part inspection request but before saving the result. Fairino FR5 may have continued; our local file still says pending. We're in a small production inspection area, using a sample housing. The startup helper resubmits pending jobs automatically. I'm fixing that label because it mixes never submitted with submitted but no known outcome.

5 replies

NO
NoraBrown0931
Replying to GraceBell0668

@GraceBell0668 Inspect the last persisted record for the attempt and any acceptance evidence carrying the same identity, keeping it out of automatic resubmission while you compare them.

14 points
GR
GraceBell0668
Replying to NoraBrown0931

@NoraBrown0931 Our last durable entry is submission intent. Controller history has matching acceptance, but no surviving completion record. I've kept it out of the resend queue.

20 points
NO
NoraBrown0931
Replying to GraceBell0668

Keep it uncertain and reconcile by identity. Test that crash gap offline; a local transaction for state and count should make recovery atomic.

9 points
GR
GraceBell0668
Replying to NoraBrown0931

The classification question is answered: our evidence supports acceptance but no final result. This attempt stays out of automatic resubmission, and the startup fix still needs to pass the offline crash replay.

10 points
NO
NoraBrown0931
Replying to GraceBell0668

That classification follows the evidence, and the replay condition keeps the startup-fix claim appropriately limited.

19 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.