Every import is listed with what went in and what didn't. A failed import names the row and the reason, which is what you fix before trying again.

The table

The history sits under the import steps on Settings, then Data Imports, newest first, with Load more for older ones.

ColumnShows
CreatedWhen it was started, and by whom
Datasource, Format, LocationWhat was imported, in which format, into which location
FileThe uploaded file's name
RowsRows in the file
StatusPending while queued or running, then completed or failed
ResultRows added, updated and skipped, or the error that stopped it
The import history table on the Data Imports page listing imports with Created, Datasource, Format, Location, File, Rows, Status and Result columns.
Import history with a completed patient import of 412 rows and a failed appointment import showing its row error.

Reading a failure

A file is one batch, so one bad row stops the lot: Nothing was imported — the whole batch was rolled back after an error. The Result names the row: Row 57: duplicate of existing record #1043, Row 12: duplicate key also seen earlier in this file, or the field problem on that row. Fix the row in the file, or choose a different If a row already exists option, and import again; with Skip duplicates a repeat run is safe. A file that could not be read is usually the wrong format for the datasource, or a spreadsheet saved as something other than CSV.