Unverified50% confidenceFactExact time
Because the sender keeps retrying when it does not receive a 2xx, a webhook endpoint may receive the same event multiple times, so the processing logic must implement idempotency.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWebhook服务商通常在首次回调超时或收到非2xx响应时自动重试，常见策略是指数退避重试3-5次73% similarUnverifiedFor creation-type endpoints, if the endpoint is not idempotent, retrying due to a timeout will create two tasks, resulting in duplicate charges68% similarUnverifiedIn message-passing scenarios, sending a value corresponds to one move, and after sending, the original holder can no longer use it; this is a manifestation of the affine constraint, enabling the compiler to statically detect errors such as double sending or using an already-sent value.67% similarUnverifiedIdempotency means that no matter how many times the same operation is performed, the result is the same as performing it once; in mobile network environments, users are prone to submitting the same request repeatedly due to unstable signals.66% similarUnverifiedRetries must be paired with idempotency design; otherwise, network jitter may cause duplicate order charges or repeated tool executions.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1023235API
curl https://kongchang.com/api/v1/knowledge/claims/1023235MCP
get_claim(id=1023235)