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