Build a useful investigation brief
Map session ownership
Record which session or token identifies the cart at each step and when it changes. Compare anonymous and signed-in transitions. Check whether the same cart survives refresh, browser restart, and an explicit sign-in choice without assuming a session boundary is the cause.
Follow redirect state
Inspect return parameters, history state, and payment or address step recovery in controlled runs. Compare the cart and selected shipping before and after return. Note missing, duplicated, or stale state and the message that asks the shopper to continue.
Reconcile financial state
For interruptions after payment submission, compare payment attempt, order candidate, confirmation, and retry controls. Test status lookup or resume paths. Document any missing correlation so a UI prompt is not mistaken for proof that no order exists.
What to carry forward
The brief is ready when another engineer can replay the guest state and identify where continuity, redirect, or financial correlation breaks. Deliver session and cart timeline, recovery UI, durable records, and unresolved hypotheses before selecting a fix.
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