Build a useful investigation brief
Map eligibility inputs
List every rule used for the failing code: dates, products, quantities, customer state, minimum amount, and stacking behavior. Compare the request's normalized values with the rule record or fixture. Identify any input that is omitted, transformed, or read from an older cart state.
Follow validation and totals
Capture the validation response, discount line, and recalculated total. Check whether the UI trusts a stale response, applies a discount twice, or clears a code without updating the total. Compare a valid neighboring code to isolate the branch that differs.
Inspect persistence
Run the safe order path and compare the discount stored on the order with the checkout summary. If the order is rejected, verify no partial promotion state remains. Preserve request order and timestamps so a delayed response is distinguishable from a rule mismatch.
What to carry forward
The investigation should let another engineer replay the exact offer and cart state and observe the same validation or amount difference. Deliver the rule inputs, response sequence, persisted outcome, and unresolved hypotheses before selecting a change.
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