Kiro is having trouble responding right now

[kienbui1995]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

ubuntu 24.04

Kiro Version

CLI 1.24

Bug Description

⠹ Thinking...
WARNING: Retry #2, retrying within 5s..
⠏ Thinking...
WARNING: Retry #3, retrying within 5s..
Kiro is having trouble responding right now:
0: Failed to send the request: An unknown error occurred: InternalServerException
1: An unknown error occurred: InternalServerException
2: unhandled error (InternalServerException)
3: service error
4: unhandled error (InternalServerException)
5: Error { code: "InternalServerException", message: "Encountered an unexpected error when processing the request, please try again.", aws_request_id: "**" }

Location:
crates/chat-cli/src/cli/chat/mod.rs:1176

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Steps to Reproduce

Request normally

Expected Behavior

I can request normally

Conversation ID

aws_request_id: "b30cf1f4-820e-4aa9-a451-a0c7f8e77315"

Additional Context

No response

[AnilMaktala]

Hey @kienbui1995, Thanks for raising this. Are you still experiencing this issue?

[AvinashDalvi89]

Most of time this issue keep coming. Today also got the same issue.

Kiro is having trouble responding right now: 
   0: Failed to receive the next message: request_id: 25035113-d6e6-4855-bf4d-e6241f5b899d, error: InternalServerError: Encountered an unexpected error when processing the request, please try again.

Location:
   crates/chat-cli/src/cli/chat/mod.rs:1442

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

[AnilMaktala]

Hey @AvinashDalvi89, thanks for reporting this.

Based on the error pattern — retries followed by InternalServerException — this looks like it could be an intermittent server-side issue rather than anything on your end.

A few questions to help us track this down:

• Frequency — Is this happening consistently or does it come and go? Does retrying after a few minutes usually work?
• Time of day — Have you noticed any pattern around when it occurs? (e.g., peak hours)
• Request type — Does it happen with all prompts or only with larger/more complex requests?

If you hit this again, running with RUST_BACKTRACE=1 as suggested in the error output and sharing the full trace would help the team investigate further.