Skip to content

fix(sdk): retry callTool on transient network errors - #363

Closed
drmikecrypto wants to merge 1 commit into
google-labs-code:mainfrom
drmikecrypto:fix/calltool-transient-retry
Closed

drmikecrypto wants to merge 1 commit into
google-labs-code:mainfrom
drmikecrypto:fix/calltool-transient-retry

Conversation

@drmikecrypto

Copy link
Copy Markdown

Reconnect and retry once when fetch fails with socket closed or similar transient errors during concurrent MCP requests.

Fixes #114

Reconnect and retry once when fetch fails with socket closed or similar transient errors during concurrent MCP requests.

Fixes google-labs-code#114
@davideast

Copy link
Copy Markdown
Collaborator

Reconciled and merged into main via #376 (transient socket/fetch errors normalized to StitchError(NETWORK_ERROR) with automatic reconnect inside the callTool retry loop for idempotent reads).

@davideast davideast closed this Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

callTool does not retry on transient network errors (socket closed during concurrent requests)

2 participants