Decide where the work belongs
Separate latency from ambiguity
Queue a delay that eventually confirms with clear waiting copy behind a case where the shopper cannot tell whether an order exists. Elevate any path that exposes a retry while order state is unknown. Record observed times instead of inventing a service target.
Describe affected scope
Compare devices, browsers, order value, fulfillment choices, and payment outcomes using available evidence. Include support reports only when their state can be verified. Mark unmeasured scope unknown rather than treating one slow test as universal.
Choose containment
Prefer a safe status lookup, disabled retry until state is known, or explicit waiting state with a recovery route. If manual review is needed, define who owns it and how the shopper avoids resubmitting. Keep the containment reversible and time-bound.
What to carry forward
Prioritize confirmation work highest when the delay leaves payment or order state unknown and exposes duplicate action. Otherwise queue a measurable latency or copy improvement with evidence of the affected path and a truthful recovery owner.
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