Resolve a connected CSV fetch error
Master Beneficiary Registry · Resolve a connected CSV fetch error · all · Published version 9
Public task guidance
Provisional guidance
Recover when the connection is unavailable or Data Imports cannot read the response.
What to do
- Note the selected source, error and time. Use the same Registry login and select the same source under New import. Use Fetch and validate to reopen a saved batch whose response was lost. This works from another browser, including when both browsers retry together. If the workspace asks you to choose a match, open Transfers. Select Refresh history and use the batch reference because connected batches can share a filename.
- When the batch is reopened, continue from its current status. Use Fetch a new CSV only when you intend to start a separate import from that source. Repeat that action from the same earlier batch to find its separate import. To resume the original, open it by reference in Transfers.
- If the fetch never saved a batch, use the same action again once the source is available. Ask the integration administrator to verify the endpoint, credentials and CSV response if the error persists.
What you need
The endpoint requires HTTPS and a CSV response. Integration administrators check any server-side access credential.
Next step
Continue from the existing batch’s current status. Review a draft in Reconcile records. For a batch already sent to the Registry, check or refresh its receipt in Transfers.
Source · Live Master Registry Data Imports connector response and error handling