[BUG] API timeout retry regression in 1.0.8
Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Activity 12 comments · opened Jun 2, 2025 · closed Jun 2, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [X] Anthropic API
- Claude CLI version: 1.0.8
- Operating System: Ubuntu 24.04
- Terminal: gnome-terminal
Bug Description
Claude Code no longer retries automatically after API timeouts. Previous versions did retries with exponential backup, but 1.0.8 just gives up immediately. Example:
╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code! │
│ │
│ /help for help, /status for your current setup │
│ │
│ cwd: my_cwd │
╰───────────────────────────────────────────────────╯
What's new:
• Fixed Vertex AI region fallback when using CLOUD_ML_REGION
• Increased default otel interval from 1s -> 5s
• Fixed edge cases where MCP_TIMEOUT and MCP_TOOL_TIMEOUT weren't being respected
• Fixed a regression where search tools unnecessarily asked for permissions
• Added support for triggering thinking non-English languages
> git commit the staged changes
⎿ API Error: Request timed out.
>
12 Comments
Hi @thomasj02, can you confirm a couple things:
ANTHROPIC_LOG=debug DEBUG=*or--debug --verbose, do you see ax-should-retryheader being returned by the backing API, or is this just failing to connect entirely?No. Only started seeing it 1.0.8. I am using the bedrock provider.
Thanks for calling out that you're seeing this in Bedrock too. Can you check the debug flags mentioned above @rajulbhatnagar ?
The same on mac os. Worked fine with v1.0.7.
When the context reaches its limit, Claude Code does not automatically 'compact' and stops after an error occurs. (1.0.8)
⎿ API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"input length and max_tokens exceed context limit: 174975 + 32000 > 200000, decrease input length or max_tokens and try again"}}
This should be feeling better in 1.0.9. @thomasj02 @solomkinmv @hikmat-subscript @rajulbhatnagar mind upgrading and reporting back if it's feeling better for you?
claude updateto force an upgradeFixed for me, thanks
Retry handling works like before in 1.0.9. Thanks
I'm actually still having a problem in 1.0.9. It seems to retry once and then give up:
Same here. And a lot of timeouts compared to before.
It actually seems somewhat random how many tries it does before giving up
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.