Unverified50% confidenceFactExact time
For external tools without an idempotency key, the second run after a failure is a real replay, and the target system receives two calls.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe smart retry mechanism in v2.0 retries only the failed targets when sending to multiple destinations, rather than resending to all of them.74% similarUnverifiedFor agent workflows, retries must carry the same idempotency key; if a new key is generated on every retry, the idempotency protection is completely defeated.72% similarUnverifiedAfter keeping the tools and setting reasoning_effort to 'none' and retrying, tool calling returned to normal, and latency dropped from 4–5 seconds to 2 seconds.68% similarUnverifiedWhen the primary channel fails, the backup channel must be able to independently complete the core task, rather than merely reproducing the same failure in a different form.67% similarUnverifiedAfter adopting the registry approach, when new instructions caused an increase in tool call failure rates, the team could perform rollbacks by reverting the environment pointer without needing to rebuild or redeploy.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1069583API
curl https://kongchang.com/api/v1/knowledge/claims/1069583MCP
get_claim(id=1069583)