Unverified50% confidenceSolutionExact time
On the Bedrock integration side, the SDK now raises API errors for exception frames and error frames in the eventstream, rather than silently handling them.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/4/2026
First Seen
Valid until: 1/2/2027
Sources
Related Entities
Related Claims
UnverifiedSDK v3.20.0 now retries on unmapped TLS transport errors.60% similarUnverifiedv3.20.0 clarified and supplemented error response documentation for several interfaces, including batch errors, file and upload errors, fine-tuning and model errors, and Responses not-found errors.59% similarUnverifiedThe update fixes an issue where claude -p and Agent SDK sessions could hang without output after an internal error; they now report the error and exit with exit code 1.59% similarUnverifiedWhen the core package's interface changes but the sub-packages have not been updated in sync, type mismatches or abnormal runtime behavior may occur, and such issues often do not surface as compile-time errors but instead appear as hard-to-reproduce runtime bugs.58% similarUnverifiedFor nested operations where a sub-operation fails but the parent operation catches the error and continues running, Dllog may exhibit a silent failure risk where the failure is swallowed and the logs are discarded along with it.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/971432API
curl https://kongchang.com/api/v1/knowledge/claims/971432MCP
get_claim(id=971432)