简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
Why retry a UR5e job when pending doesn't mean unsent?
VictorAbbott0011 · 2025年11月1日 13:52 UTC
已关闭Our startup helper resends pending housing checks after a crash. Some were already sent. Missing result isn't enough.
11 条回复
What persists before sending: attempt identity, intent, or nothing?
5分Identity and pending entry. Nothing records whether the send reached the receiver.
19分Keep that uncertain attempt out of resubmission while its outcome is checked.
7分Who reviews it, and can they see which housing and original attempt are held?
17分No receipt still wouldn't prove it was unsent. Recovery must allow an unknown outcome.
18分Review goes to quality with the housing and attempt ID. Automatic retry removed from the test build.
15分Does that hold survive another restart?
20分Proposed state is persisted. Restart test not run yet.
7分Also settle who may authorise another attempt; reviewing a row should not itself restart the job.
8分And preserve the old identity if a late result turns up during review.
10分Any result from the restart test, or still proposed?
5分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .