Our application crashed after sending a sample acceptance checking request but before saving the result. Universal Robots UR5e may have continued; our local file still says pending. We're in a small production inspection area, using a reference plate.
The startup helper resubmits pending jobs automatically. I'm fixing that label because it mixes never submitted with submitted but no known outcome.
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.
@OliverBrown0885 Keep it uncertain and reconcile by identity. Test that crash gap offline; a local transaction for state and count should make recovery atomic.
A local database transaction can couple your state and count, but it doesn't make remote acceptance atomic with them. Your recovery claim needs that limitation.
Exactly; my wording was too broad. The transaction protects local accounting. Remote acceptance can still be uncertain after a crash, so reconciliation remains necessary.
@JamieBarnes0556 The classification question is answered: our evidence supports acceptance but no final result. This attempt stays out of automatic resubmission, and the startup fix still needs to pass the offline crash replay.