Decide where the work belongs
Identify the observable consequence
Compare intended and final record sets for each controlled blank form. Record unwanted empty entries, lost valid records, and incorrect source locations separately. Distinguish an inconsistent progress count from a persistent state change, while recognizing that a misleading count can still make users uncertain whether their import completed correctly.
Scope the file-producing patterns
Identify exports that add trailing blank lines, spacer rows, or empty-field records. Compare their outcomes with files from the same producer without those patterns. Estimate relevant reach rather than assuming every file containing a newline is exposed or every apparent blank row should be handled under one shared rule.
Assess correction and expectation clarity
Review the preview and supported format guidance for blank handling. Try the correction path without altering quoted multiline content. Include the effort required to distinguish a real empty record from a spacer, especially when the current error location or summary count gives users no reliable source reference.
What to carry forward
Record priority with the affected blank structure, persistent or user-facing consequence, producer reach, and recovery effort. Assign a trigger for lost valid records or unwanted accepted entries. Keep the decision grounded in a defined handling contract rather than a blanket preference to ignore every blank-looking source row.
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