Summary
This article explains how to download error files, how to interpret the summaries contained in those files, and how to correct validation errors that are reported. It also covers the steps to take to recover when a job fails or when a job remains stuck in progress. Each section provides practical instructions to help you diagnose problems and complete the necessary recovery actions.
Download the original file and error report
Use the Bulk Search job history table for file-level downloads.
- Original file: Select the underlined file name to download the uploaded CSV.
- Error report: Select Download in the Error Report column when one or more rows failed validation.
- No error report: An em dash [ - ] means every submitted row passed validation.
Understand job summaries
A completed job may include both results and an error report. This is expected when valid rows ran while invalid rows were skipped.
| Job outcome | What it means | What to do |
|---|---|---|
| Complete, no error report | All submitted rows passed validation and completed processing. | Review or export the results. |
| Complete, error report available | Valid rows completed; one or more invalid rows were skipped. | Download the error report, correct those rows, and upload them again if needed. |
| Failed, error report available | The file could not be processed or no row passed validation. | Review the job message and error report, correct the file, and upload it again. |
| Processing | The job is still queued or running. | Wait for completion before exporting results. |
Review validation errors
The error report echoes each failed row as uploaded, includes the original row number, and lists every validation error found. Correct only the affected rows and upload them in a new file.
| Error code | Meaning | Correction |
|---|---|---|
INVALID_NPI |
The NPI is not 10 digits beginning with 1 or 2. | Enter a valid 10-digit NPI. Dashes and spaces are removed automatically. |
INVALID_TIN |
The TIN is not exactly 9 digits after non-digits are removed. | Enter the correct 9-digit TIN. |
INVALID_FIRST_NAME_LENGTH |
The first name is outside the 2–40 character range. | Correct the first name. |
INVALID_LAST_NAME_LENGTH |
The last name is outside the 2–40 character range. | Correct the last name. |
NAME_PAIR_INCOMPLETE |
Only one of first name or last name was provided. | Provide both names or remove both. |
INVALID_ORG_NAME_LENGTH |
The organization name is outside the 2–200 character range. | Correct the organization name. |
NO_SEARCH_FIELDS |
The row contains no searchable identifier. | Add an NPI, TIN, organization name, or complete first and last name pair. |
Troubleshoot failed jobs
| What happened | What you see | Recommended action |
|---|---|---|
| Unreadable file | “We couldn't read this file.” The file may be empty, not UTF-8, or missing required headers. A failure email is sent to you. | Re-export the file from the Bulk Search template as a UTF-8 CSV and upload it again. Nothing ran and nothing was charged. |
| Zero valid rows | The same unreadable-file message. The error report lists every row. | Download the report, correct the rows, and upload them again. Nothing ran and nothing was charged. |
| Upload never finished | The job remains Processing shortly after upload with no progress. | The upload link expires 15 minutes after Start Search. Create a new upload rather than waiting on an incomplete upload. |
| Job is processing for a long time | The job remains Processing. | Large files can take hours. If progress hasn't moved in several hours, contact support@providertrust.com with the file name. |
| Download link expired | The original-file or error-report link no longer opens. | Return to job history and generate a fresh link. |
Operational recovery checklist
- Confirm the job status and open the job detail page.
- Download the original file and error report, if available.
- Identify whether the issue affects the full file or only individual rows.
- Correct invalid rows using the error code guidance.
- Re-upload corrected rows as a new Bulk Search job.
- Escalate infrastructure or persistent processing issues with the job ID, file name, client, and observed error.
Comments
0 comments
Please sign in to leave a comment.