Establish what is happening
Locate a known invalid source value
Choose a controlled file with one unmistakable validation failure and record its logical row, physical line range, and source column. Include the header position. Compare the displayed error location with these references rather than searching a large file for a value that might appear in several different records.
Identify the numbering convention
Determine whether the error counts headers, skipped lines, or multiline fields. Check whether filtered preview rows receive new positions. A one-row offset may come from header handling, while a growing offset after quoted newlines suggests the report is mixing physical line numbers with logical record numbers.
Compare source and destination labels
Record whether the error names the source heading, mapped destination field, or an internal validation attribute. Follow the approved mapping for the failing value. If the location is correct but the label is unfamiliar, keep a copy or mapping explanation issue separate from an actual row-coordinate defect.
What to carry forward
Finish with the invalid value, independent source coordinates, displayed location, and the convention that first diverges. State whether users can still identify the record through another stable reference. The next owner should know whether to inspect row offsets, multiline counting, mapping labels, or missing location context.
Technical background: DuckDB documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow