Keep the lesson for the next incident
Document the approved input set
List the file identity, mapping revision, and options that define the reviewed import. Explain which later changes require a refreshed preview or another confirmation. Keep the contract connected to execution loading so a mutable settings reference is not mistaken for a captured approval of a specific input revision.
Retain a distinguishable revision sequence
Keep small same-named files with different values and mappings, plus the navigation or delayed-execution sequence that caused drift. Record expected final assignments. The fixture should make the consumed revision visible without production logs or customer content and remain understandable when the preview layout changes.
Review mutable input additions
Assign review when another import option, editable mapping source, or asynchronous step is introduced. Ask where its value is captured and how changed state reaches the user. Track confirmed preview mismatches separately from generic import errors because an unapproved assignment can still complete successfully and pass field validation.
What to carry forward
Close with an explicit confirmation contract, a reproducible revision sequence, and an owner for future input changes. Keep historical reconciliation separate from prevention. The next maintainer should be able to identify the exact work the user reviewed and explain why execution cannot silently substitute a later file or mapping.
Technical background: Django import-export 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