Reconcile a blocked repeat Registry row
Confirm whether the affected source key already has a receipt or is still in a native Registry job.
Provisional sandbox guidance
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.
Before you start
A duplicate correction stays blocked from transfer after approval. Preserve the earlier receipt and both audit trails.
What happens next
Confirm which rows were already received and share the evidence with the Field Agent and First Reviewer. For failed jobs, check the saved rows and receipt logs. If the job saved the row, keep the alternate row blocked and investigate the existing job. For a confirmed outstanding row, refresh the earlier receipt, then reopen the already-approved correction and check whether the hold cleared. Older jobs without saved-row tracking need native reconciliation before resubmission.