Decide where the work belongs
Separate rejection from silent acceptance
For each representative file, record whether import stops, asks for a delimiter, or continues with incorrect columns. Give silent acceptance particular attention when downstream validation cannot detect misplaced text. Keep observed outcomes separate from corruption that is merely suspected.
Group by file producer
Compare exports from the actual tools and locales customers use. Estimate reach from attempted imports and their outcomes, not just tickets. One widely used semicolon export can affect more work than many malformed files from an unsupported custom source.
Assess the existing recovery path
Try the available format selector or documented re-export steps using the original example. Record the extra effort and whether users can recognize the correct preview before committing. A workaround only reduces urgency when it produces a reliable, understandable result.
What to carry forward
Record a queue decision with the affected producer, failure mode, workaround cost, and evidence for reach. Assign a review trigger such as a newly accepted wrong mapping or a new export format. Avoid treating all delimiter-related reports as one equally urgent defect.
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