When errorRows is greater than zero on an ImportBatch, the batch cannot be fully committed until those rows are addressed. Each error row has a corresponding ImportValidationIssue with error-level severity, describing what went wrong — for example, an unrecognized analyte code, a missing required field, or a resultValue that could not be parsed. Compliance staff must either resolve each issue using a suggestion or overrideValue, or exclude the row, before the batch status can advance to committed and valid results can be written to the site record.
piper
Import Batch Error Rows
The `errorRows` on an ImportBatch counts rows where validation found critical problems that block those rows from being committed as AnalyticalResults.