Why retry a UR5e job when pending doesn't mean unsent?
VictorAbbott0011 · 1 Nov 2025, 13:52 UTC
ClosedOur startup helper resends pending housing checks after a crash. Some were already sent. Missing result isn't enough.
11 replies
What persists before sending: attempt identity, intent, or nothing?
5 pointsIdentity and pending entry. Nothing records whether the send reached the receiver.
19 pointsKeep that uncertain attempt out of resubmission while its outcome is checked.
7 pointsWho reviews it, and can they see which housing and original attempt are held?
17 pointsNo receipt still wouldn't prove it was unsent. Recovery must allow an unknown outcome.
18 pointsReview goes to quality with the housing and attempt ID. Automatic retry removed from the test build.
15 pointsDoes that hold survive another restart?
20 pointsProposed state is persisted. Restart test not run yet.
7 pointsAlso settle who may authorise another attempt; reviewing a row should not itself restart the job.
8 pointsAnd preserve the old identity if a late result turns up during review.
10 pointsAny result from the restart test, or still proposed?
5 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .