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

Which housing jobs can startup still submit after this crash?

NathanArcher0373 · 2026年8月20日 14:26 UTC

回复讨论
NA
NathanArcher0373
My UR5e inspection application crashed after sending a housing request but before saving its answer. Startup resends everything marked pending, including untouched jobs and possibly completed ones. What can I separate without guessing what the receiver did?

16 条回复

PR
PriyaBarnes0568

Stop blanket resubmission first; pending is not evidence that a request never left.

22
AN
AnnaBell0677

Who can reconcile a housing when the file and the receiver disagree?

9
AM
AmyBennett0728

Anna's question needs an actual person, but they also need somewhere to leave it undecided. A supervisor choosing between resend and complete is still guessing if both buttons require evidence they haven't got.

16
NA
NathanArcher0373

Automatic resend is disabled. The cell lead owns reconciliation; the existing file only has pending or done.

10
DA
DavidBrooks0867

I'd make a small offline copy with a housing that has definitely never reached the send step and another stopped after that step starts. Restart both. You want to see the first eligible for normal submission and the second held for reconciliation, without needing a robot to demonstrate the difference.

22
AM
AmyBennett0728

David, a send-step flag written afterwards leaves the same crash gap. The durable record has to capture the intent before the possible external effect, and a crash there still leaves uncertainty rather than proving delivery.

13
DA
DavidBrooks0867

Yes, I was too loose about the boundary. I meant a persisted intent before calling out, not a note afterwards. The test should interrupt on both sides of that write as well as around submission and result storage; otherwise it can pass while keeping the original hole.

15
AN
AnnaBell0677

Does reopening a held record preserve the hold, or quietly turn it into pending again?

8
PR
PriyaBarnes0568

Also test an old saved result arriving after restart. It must not complete a different attempt.

7
NA
NathanArcher0373

Found that exact reopen problem in the offline copy. Unknown states were loaded as pending by default.

8
AM
AmyBennett0728

That default needs a test of its own. Include a state the current program doesn't recognise, not just the new hold state, so an older installation cannot silently reinterpret a newer file as work to send.

11
DA
DavidBrooks0867

And keep the original file format version with the record. I'm not suggesting the software magically understand a future format; refusing to offer submission is a valid response when it cannot interpret the evidence it loaded.

9
NA
NathanArcher0373

Parser now refuses unknown states. Repeated reopen preserves the uncertain housing, and the unsent example stays separate. Receiver lookup still unconfirmed.

20
AN
AnnaBell0677

Then the lead needs an unresolved list, not a promise that every held housing will be recoverable.

20
NA
NathanArcher0373

Added that list. Offline crash tests pass around intent, send and save; actual receiver correlation remains with the integrator.

10
PR
PriyaBarnes0568

Keep automatic retry off for those legacy pending records; the new parser cannot reconstruct their missing history.

4

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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