Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Seeking Help: Claude 4 Unavailable & Claude 3.7 Frequent Interruptions on Amazon Q Developer

3

Hello re:Post community and AWS Team,

I'm experiencing persistent issues with Amazon Q Developer and am hoping to get some insights or solutions from anyone who might have encountered similar problems.

My main issue is that Claude 4 (the model I primarily intend to use) is consistently unavailable. I keep getting the message: "Model Unavailable The model you've selected is experiencing high load. Please switch to another model and try again." This has been ongoing for several days now.

Furthermore, when I switch to Claude 3.7 as a fallback, I find that it frequently interrupts my workflow, making it difficult to work smoothly and efficiently.

I'm curious to know:

Is anyone else experiencing similar issues with Claude 4 unavailability or frequent interruptions with Claude 3.7 on Amazon Q Developer?

Does anyone know why these issues are occurring and if there's an estimated timeline for when they might be resolved?

Are there any temporary workarounds or troubleshooting steps I can try, other than just switching between models, to improve access or stability?

Thanks in advance for any information or help you can provide!

Topics
Business ApplicationsMachine Learning & AI
Tags
Amazon QAmazon Q Developer
Language
English
asked 10 months ago1.6K views
4 Answers
2

This also happens to me for almost a week now. I'm on Q Developer subscription. Both Q Developer on VSCode and CLI can't use Sonnet 4 model.

Also reported here with screenshots and log: https://github.com/aws/aws-toolkit-vscode/issues/7720

answered 10 months ago
  • MyXi
    10 months ago

    Hi b3cak,

    Yes, I'm facing the exact same issue! Especially that message: 'Model Unavailable. The model you've selected is experiencing high load. Please switch to another model and try again.' It's really hindering my work.

    I sincerely hope that AWS can help resolve this problem, or at least suggest a way to get Claude 4 working smoothly again as soon as possible.

2

I'm sadly having the same experience. Actually not only for Claude 4 Sonnet, but also for the 3.7 version I receive all the time the message that they experience high load and I should use a different model. With this limitations it is not useable at all and I have to consider switching to a different coding assistant...

answered 10 months ago
0

Based on the information available, there are a few things to note about your experience with Claude models in Amazon Q Developer:

For Claude 4 Sonnet access in Amazon Q Developer CLI, you need to be using version 1.11.0 or newer. You can access it through several methods:

  • During an active chat, use the /model command and select claude-4-sonnet
  • Start a new chat with q chat --model claude-4-sonnet
  • Set it as your default model using q settings chat.defaultModel claude-4-sonnet

Regarding the interruptions and availability issues you're experiencing, these appear to be related to known service capacity challenges. Some users have reported similar problems with Amazon Q, including error messages indicating service disruptions. These issues can occur due to high demand following recent launches, which can strain the service capacity.

For troubleshooting the interruptions with Claude 3.7, you could try:

  1. Running the q doctor command to diagnose common issues with your Amazon Q installation
  2. Ensuring you're properly authenticated by running q login if needed
  3. Breaking down your prompts into smaller, less complex inputs
  4. Checking if there are any network connectivity issues, particularly with port 8443 which Amazon Q uses

The AWS team is reportedly aware of these issues and working on stabilizing the service and provisioning additional capacity. Unfortunately, there's no specific timeline mentioned for when these issues will be fully resolved.
Sources
Access Claude Sonnet 4 in Amazon Q Developer CLI | AWS DevOps & Developer Productivity Blog
Amazon Q is having trouble responding right now: | AWS re:Post

answered 10 months ago
AWS
EXPERT
reviewed 10 months ago
  • MyXi
    10 months ago

    Thanks for the suggestions. I've performed some troubleshooting and unfortunately, the core issue persists.

    My Amazon Q CLI version is up-to-date, which should support Claude 4 Sonnet:

    q --version q 1.12.6

    However, I consistently receive the "Model Unavailable" message when trying to use it:

    hi

    The model you've selected is temporarily unavailable. Please select a different model.

    ✔ Select a model for this chat session · claude-4-sonnet (active)

    Using claude-4-sonnet

    To rule out local network issues, I also checked connectivity to the Amazon Q API endpoint on port 8443. The test was successful:

    Test-NetConnection -ComputerName qbusiness.us-east-1.api.aws -Port 8443

    ComputerName : qbusiness.us-east-1.api.aws RemoteAddress : 100.24.201.181 RemotePort : 8443 InterfaceAlias : Wi-Fi SourceAddress : 192.168.1.137 TcpTestSucceeded : True

    This confirms my local setup and network aren't blocking access. It strongly suggests the problem is related to service capacity or high load on AWS/Anthropic's end for Claude 4 Sonnet.

    Is there any official update on when these capacity issues are expected to be resolved? This ongoing unavailability significantly impacts my work, especially as a paying customer.

    Thanks for any further insights or information!

0

I have the same issue, at least twice a day I get notified the Sonnet model is unavailable. Now it is also Sonnet 3.7 as well. I can confirm it has nothing to do with network connections. I agree with others as this makes the service not useable or worth the money. Why doesn't AWS use their own foundational models instead of Claude?

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content