An intermittent problem is easier to investigate when the steps leading to it are repeatable. Record the starting screen, selected action, expected result and actual result. Keep the sequence short and avoid changing several unrelated settings between attempts, which makes one occurrence difficult to compare with another.
Use a stable starting point
Begin from the same profile and screen when possible. A fresh app launch and a return from standby can lead to different states. Record which one preceded the failure rather than treating them as equivalent.
Record frequency honestly
Say “twice in five attempts” if that is what you observed. Do not turn one occurrence into “always” or a brief successful retry into “fixed forever.” A small observation is still useful when its limits are clear.
Keep testing proportionate
Repeatedly triggering a login or purchase action can create new problems. Stop when you have enough evidence to describe the issue, and use support for the next step. Do not submit duplicate payments to test a screen.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
“Open the saved profile, enter Sport, select the same station, then press Back: the list freezes in two of five tries” is more reproducible than “sometimes slow.”
Questions about this topic
Does one successful retry prove a permanent fix?
No. Report the observed result and its limited sample.
Should I repeat a payment to reproduce a problem?
No. Preserve the error and transaction reference instead.