Ask the local knowledge assistant
NSIPA knowledge library
Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.
534 published entries across 18 services · 64 source-linked guides
2 matching entries · Page 1 of 1
Reconcile a saved Registry row with a missing receipt log · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
The Registry saved the row and recorded that save in the same transaction. The normal receipt log is still missing for the indicated row.
What to do
- Open Reconcile records and check Registry saved, receipt log missing. Use Download audit report and keep the original batch and Registry references.
- Field Agent: Report the missing receipt log to the Registry Administrator. Keep the saved row out of follow-up corrections.
- First Reviewer: Keep the existing approval and use the original and alternate batch references to follow the reconciliation.
- Registry Administrator: Compare the saved-row evidence with the native job and receipt log. If both retries have ended and the log is still missing, keep the failed attempts with the incident evidence. Coordinate with Registry integration support to retry the existing native job once the log error is resolved. Refresh the original receipt to verify the restored log.
What you need
A saved row continues to block alternate transfers for its source key. Native retries reuse the same saved row and share the same receipt, even if they overlap. If another worker is still retrying when a worker fails, keep the alternate blocked and refresh the original receipt when the retry settles.
Next step
Resolve the missing log against the original transfer. After both retries fail, ask Registry integration support to retry that same job once the log error is resolved. Keep the saved row out of alternate batches throughout.
Published version 7 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Verify a restored Registry receipt log · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
The Registry restored the normal receipt log for a previously saved row on the original transfer.
What to do
- Check the original Registry reference and confirm Registry logged under Reconcile records. In Activity, look for Registry receipt log restored. Use Download audit report to retain that event.
- Field Agent: Keep the restored receipt and leave alternate transfers for the same row on hold.
- First Reviewer: Preserve the existing approval and link the restored receipt to the original and alternate batch references.
- Registry Administrator: Verify the restored log against the original job and saved-row evidence. If retries overlapped, confirm one receipt-log entry per saved row. If one worker failed after another restored the log, confirm the job stays Processed. If a later retry restored the log after both earlier retries failed, verify Processed and keep the earlier failures with the restored receipt and audit report. If a retry reaches an already Processed job, refresh the original receipt. Confirm the same Registry reference, the existing saved row and receipt log, and a single restoration event.
What you need
Retries use the original save and job reference. The attempt count can increase while the row and its receipt stay single. If a retry succeeds after an earlier worker failure, the job becomes Processed and clears the earlier job error. Once the job is Processed, any later worker failure stays in worker diagnostics. The logged row continues to block a matching alternate correction.
Next step
Use the original receipt and Registry reference for any follow-up. Where the source creates registrations, follow the relevant registration decisions separately.
Published version 6 · public guidanceOpen this guide · Download plain text
Was this guide helpful?