our fr5 acknowledgement has two possible attempts

A local sequence, but it restarts too. No shared run identifier found.

Ask controls what the acknowledgement means before assigning it; request receipt and inspection completion would tell support different things even if the matching problem were solved

Quality has it, Aisha. Naomi, the acknowledgement means request receipt only.

Then don't count it as a completed check.

Preserve each source's native order and the raw times. A merged list sorted by disagreeing clocks can create a confident-looking sequence that none of the original systems actually recorded.

Done, Alex. The merged time-sorted chart is out of the decision notes. Originals kept.

Does the incident package distinguish missing events from events whose order is uncertain? That would help the next person avoid assuming the entire lead-in is absent

Now it does. Both request records exist; the receipt's attempt assignment is unresolved.

Thanks, that is clearer. Has quality finished its separate coupon decision, or is the item still waiting because everyone is focused on the logs?

Aisha, useful question. The support report can carry an unresolved receipt without making the physical item wait indefinitely for a software match that may be unrecoverable.

Quality completed the coupon review. Receipt still unassigned; no new attempt authorised through this report.

Has support accepted the report with that gap explicit?

Yes. Investigating the timeout now, without treating the receipt as proof either attempt completed.