Build a useful investigation brief
Build a field survival map
For each field, record submitted shape, permitted value, model value, rendered value, and error state after rejection. Include blank, selected, repeated, and long values without storing sensitive content.
Trace the response path
Follow controller validation, render or redirect, object reloading, form builder values, and nested collection handling. Identify where a submitted value is replaced by a default or omitted from the response.
Compare browser recovery
Check refresh, back navigation, validation retry, and a new tab after the same rejection. Use the server response as the primary evidence and mark browser-only recovery as limited.
What to carry forward
The brief should identify the first field or response boundary that loses draft data, affected shapes, and reliable recovery paths. Conclude parameter handling, render reconstruction, redirect behavior, browser state, or unresolved with confidence. Trace permitted parameters, model assignment, validation render, redirect behavior, form builders, and nested collection reconstruction to locate where a valid submitted value disappears.
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