our startup retries a bracket check it may already have sent

The installed job has an attempt identity. The old application file saved only the bracket label, which gets reused. We cannot match this particular pending entry confidently.

Then that old entry stays uncertain. New bookkeeping cannot manufacture the identity it never saved.

Who is handling the actual bracket while you investigate? The screen change needs to match that handover, not leave someone choosing whether to load it again

Have the integrator and job owner define reconciliation for that held case, including what the operator sees and who can decide the next step; this is not a decision the parser should make from an empty field.

Shift lead owns the held bracket and its identified location; integrator owns the job-state comparison. New draft saves an attempt identity before submission and distinguishes never submitted, unresolved submission and a reconciled result.

What happens if the process stops after saving that identity but before it can establish whether the request reached the other side? That is the gap worth testing deliberately.

And test a second restart. The first hold must not become permission to retry later.

Offline interruptions on both sides of submission keep that same attempt unresolved. A second restart does too. We can still distinguish a queued entry which never entered the submission step, but no old pending row is being silently recategorised that way.

Can a covering operator tell which case needs the shift lead without opening your files? The word pending already caused trouble once

Cover could identify it from the draft screen, but read result saved as permission to continue the physical job. We changed that to name the recorded verification result and left physical continuation to the agreed job response. Another walkthrough is due.

Good distinction to test again. Has the owner reconciled the original held bracket yet, or is that still open alongside the software work?