Why retry a UR5e job when pending doesn't mean unsent?

VictorAbbott0011 · 2025年11月1日 13:52 UTC

已关闭

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

VI
VictorAbbott0011
Our startup helper resends pending housing checks after a crash. Some were already sent. Missing result isn't enough.

11 条回复

RA
RaviBell0650

What persists before sending: attempt identity, intent, or nothing?

5分
VI
VictorAbbott0011

Identity and pending entry. Nothing records whether the send reached the receiver.

19分
DA
DanielAli0217

Keep that uncertain attempt out of resubmission while its outcome is checked.

7分
AN
AnnaBell0677

Who reviews it, and can they see which housing and original attempt are held?

17分
RA
RaviBell0650

No receipt still wouldn't prove it was unsent. Recovery must allow an unknown outcome.

18分
VI
VictorAbbott0011

Review goes to quality with the housing and attempt ID. Automatic retry removed from the test build.

15分
DA
DanielAli0217

Does that hold survive another restart?

20分
VI
VictorAbbott0011

Proposed state is persisted. Restart test not run yet.

7分
AN
AnnaBell0677

Also settle who may authorise another attempt; reviewing a row should not itself restart the job.

8分
RA
RaviBell0650

And preserve the old identity if a late result turns up during review.

10分
DA
DanielAli0217

Any result from the restart test, or still proposed?

5分

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .