Our FR10 verification ticket has two attempts under one job label after restart. The acknowledgement sits between them depending on which clock I read. I have kept the original exports; where should I look next?
We once had the physical sample well identified while its software history was incomplete. That was enough for quality to review the sample separately, not enough to fill in the missing software link. Is your coupon identified?
Ask the developer to state what the acknowledgement means as well. It may acknowledge receipt of work rather than its completion, which changes what even a successful match would tell support.
It can receive the known sequence and the gap explicitly. I would ask which missing evidence matters for its diagnosis rather than hold everything back until Imran can produce a match that may no longer be recoverable.
Support has both attempts and the unmatched receipt, with the reset behaviour noted. It is reviewing the timeout; quality is handling the coupon independently