Keep the lesson for the next incident
Keep the lost state
Record query, filters, sort, page, entry context, and the action that discarded them. Mark which fields were intended to reset. This distinguishes a product contract gap from a technical regression and keeps the cost visible.
Compare later journeys
Review direct links, result returns, and narrow navigation after the change. Look for a field that survives one path but fails another. Preserve a valid and invalid URL example so the lesson includes recovery, not only the happy path.
Adopt one contract check
Add a transition table, shared-link replay, or explicit reset rule to future search reviews. Assign the practice and a revisit date. Define the observation that would show it prevented rework, such as matching results after a return action.
What to carry forward
The learning record should connect one lost search state to a repeatable navigation check and a clear persistence rule. Stop when another reviewer can apply it to a different filter path. Carry forward uncertainty for fields whose intended lifetime has not yet been decided.
Technical background: Adobe developer 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