Retries and Duplicate Requests

A single timeout can trigger retries in several places. After a checkout request times out, the customer may tap “Try again” while the client library schedules its own attempt and the original server handler is still running. One purchase intention has now produced several requests, possibly reaching different servers at the same time.

Retries help clients recover from failures, but they also create duplicates and additional load. A reliable API makes repetition safe, tells callers how to interpret uncertain outcomes, and provides a stopping point when another attempt is no longer useful.