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

VictorAbbott0011 · 1 Nov 2025, 13:52 UTC

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

11 replies

RA
RaviBell0650
Replying to VictorAbbott0011

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

5 points
VI
VictorAbbott0011
Replying to RaviBell0650

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

19 points
DA
DanielAli0217
Replying to VictorAbbott0011

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

7 points
AN
AnnaBell0677
Replying to VictorAbbott0011

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

17 points
RA
RaviBell0650
Replying to VictorAbbott0011

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

18 points
VI
VictorAbbott0011
Replying to AnnaBell0677

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

15 points
DA
DanielAli0217
Replying to VictorAbbott0011

Does that hold survive another restart?

20 points
VI
VictorAbbott0011
Replying to DanielAli0217

Proposed state is persisted. Restart test not run yet.

7 points
AN
AnnaBell0677
Replying to VictorAbbott0011

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

8 points
RA
RaviBell0650
Replying to VictorAbbott0011

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

10 points
DA
DanielAli0217
Replying to VictorAbbott0011

Any result from the restart test, or still proposed?

5 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .