Unverified50% confidenceCautionExact time
Unlimited retries cause side effects such as duplicate payments, duplicate notifications or duplicate record updates; external actions should be assigned idempotency keys, have a maximum number of attempts, and use exponential backoff with jitter.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedTo avoid retries causing side effects to be executed repeatedly, idempotency keys or request identifiers should be used to ensure that the same logical request takes effect only once.79% similarUnverifiedRetries must be paired with idempotency design; otherwise, network jitter may cause duplicate order charges or repeated tool executions.79% similarUnverifiedRetry behavior has a positive-feedback characteristic: during system overload, each retry appends additional requests to the backend, causing pressure to rise and response times to lengthen, thereby triggering more timeouts and retries and forming a death spiral.78% similarUnverifiedBlindly retrying non-idempotent operations (such as payments, placing orders, creating tasks, sending messages) may cause duplicate charges or duplicate side effects, and is a classic anti-pattern in distributed systems.78% similarUnverifiedDuring replay, it must be ensured that side effects already executed are not triggered again, which typically requires tool calls to be idempotent, or requires patterns such as the transactional outbox to bind side effects to state changes.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1057254API
curl https://kongchang.com/api/v1/knowledge/claims/1057254MCP
get_claim(id=1057254)