Establish what is happening
Identify the intended first record
Mark any introductory lines, the real header if present, and the first data record in a sanitized source. Record the expected column names and data-row count. Do not infer header presence from capitalization alone; a first record may contain values that resemble labels.
Compare labels and record position
Inspect the preview’s field labels and first visible record. Determine which source line supplied each label and whether any data row disappeared. Check whether a header row appears in validation failures as an invalid date or number, which can indicate it was processed as data.
Check the explicit header choice
Where supported, switch header detection to the known layout and compare the same source file. Keep field mapping unchanged until the row boundary is correct. If the preview changes but execution does not, retain the selected setting and import identifier for a handoff investigation.
What to carry forward
Finish with the intended header location, expected first record, detected choice, and first surface that disagrees. Separate skipped introductory lines from header inference. The next owner should be able to reproduce the missing or extra row without guessing whether the file originally contained column names.
Technical background: PostgreSQL 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