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

Recovering part inspection bookkeeping across a crash (Fairino FR5)

GraceBell0668 · 2026年7月10日 00:44 UTC

回复讨论
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 条回复

NO
NoraBrown0931

@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
GR
GraceBell0668

@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
NO
NoraBrown0931

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

9
GR
GraceBell0668

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
NO
NoraBrown0931

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

19

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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