Unverified50% confidenceFactExact time
After the fix, the payment provider's retry bug was directly exposed in the next round of testing, because the retry was actually captured instead of hitting a URL that had disappeared.
1
Sources
50%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen the retry was sent at the 25th hour, the catcher had already auto-deleted, the retry request hit a nonexistent URL and returned 404, but the payment provider's dashboard still showed "delivered".75% similarUnverifiedFixed the issue where sub-agents crashed directly upon encountering a model 404 on the first call; they will now fall back to the session's fallback model chain and return detailed error information.69% similarUnverifiedA status page marked 'Resolved' usually means the service has recovered, but whether orders that failed or were pending during the incident will be automatically retried, and whether they will cause duplicate charges, needs to be verified separately by developers on the application side.68% similarUnverifiedIn replay tests, the same requestId is submitted twice consecutively; the first time the replay flag is false, the second time it should be identified as a duplicate request with replay as true, both returning the same order number with only one business change produced.66% similarUnverifiedThe async client now retries on connection errors, and a blocking issue in the coroutine retry loop has been fixed.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1012471API
curl https://kongchang.com/api/v1/knowledge/claims/1012471MCP
get_claim(id=1012471)