Reconcile a blocked repeat Registry row Published version 4 ยท Provisional guidance Purpose Confirm whether the affected source key already has a receipt or is still in a native Registry job. Steps Open the affected row and the existing batch. Compare the mapped source key, both batch references, the native Registry reference and the row receipt. If two approved corrections competed to send the row, check Activity to confirm which batch entered the Registry queue. Refresh that receipt and coordinate any uncertain outcome with the integration owner. Requirements A duplicate correction stays blocked from transfer after approval. Preserve the earlier receipt and both audit trails. Next Step Confirm which rows were already received and share the evidence with the Field Agent and First Reviewer. If a failed native job has a row log for the affected key, keep the alternate row blocked and investigate the existing job. For a confirmed outstanding row, verify that its native job has ended and no row log exists. Refresh the earlier receipt, then reopen the already-approved correction and check whether the hold cleared. Retain both receipts when the Field Agent completes the recovery transfer.