Capture what happened
Note the target, service identifier, quantity, and approximate submission time. A network error describes what the browser received, not necessarily what the server accepted. Avoid repeatedly pressing submit while the first request's outcome is unknown.
Check history and balance
Look for a matching order and its charge in the account. If the same details appear, keep that identifier and follow its status. If records are absent or inconsistent, ask support to confirm whether the request was received before making another attempt.
Use a deliberate retry
When the original request is confirmed absent, submit once and retain the resulting reference. If several similar entries exist, identify each rather than assuming one is merely a display duplicate. Any cancellation must follow the selected service's rules.
Decision checklist
| Decision | What to check |
|---|---|
| Submission | Known request details |
| History | Matching accepted record |
| Retry | Confirmed absent original |
Worked example
A hypothetical checkout times out after submitting 700 units. Order history contains one matching request and a corresponding deduction. The browser error does not justify another 700-unit purchase; the recorded order is the next item to inspect.
Example figures explain the decision; they are not current prices or promised results.