NSIPADocumentation
Open platform

Follow a correction blocked by an earlier Registry transfer

Check the earlier receipt before you continue with the affected batch.

Provisional sandbox guidance

Steps

  1. If the warning offers Reload batch, use it to update the affected rows. Open the affected row in Reconcile records and select Open existing batch when the button is available. Ask the Registry Administrator to verify the receipt if it belongs to another account.
  2. If the status is Registry transfer in progress, select Refresh Registry receipt on the earlier batch and wait for the earlier receipt to settle. Reopen the blocked batch to see the updated row status. If it is Already received by Registry, keep the existing source key and exclude the row from an editable batch.

Before you start

An approved batch with a conflict stays blocked from transfer. Ask the Registry Administrator to reconcile the approved batch before taking further action.

What happens next

If the earlier correction failed, ask the Registry Administrator to confirm that the native job has ended and check whether the Registry logged the row or recorded its save. A saved row keeps the alternate blocked even if that native job failed. For a confirmed outstanding row, refresh the earlier receipt, then reopen the already-approved correction. If Transfer to Registry is available, transfer that batch and check its receipt. If all rows were already received, leave the repeat batch unsubmitted. Keep the existing receipt.