Recovering inspection-cycle execution bookkeeping across a crash (Universal Robots UR5e)

AdaBennett0738 · 2 Jun 2026, 22:39 UTC

Reply to discussion
AD
AdaBennett0738
I'm fixing our startup bookkeeping after a crash between sending a inspection-cycle execution request and saving its result. The setup uses Universal Robots UR5e in a workshop fixture inspection cell, with a sample housing. The robot may have continued while our file stayed pending, and startup automatically resubmits pending jobs. That state currently covers both unsubmitted and uncertain work.

2 replies

JO
JoAli0244
Replying to AdaBennett0738

What is the last durable entry for this attempt? Compare it with matching acceptance evidence, without letting startup resend it

21 points
AD
AdaBennett0738
Replying to JoAli0244

@JoAli0244 I've found persisted submission intent and matching acceptance in the controller history, without a surviving completion record. This attempt is excluded from our automatic resend queue.

23 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.