Frequent Service is busy / retry warnings in Kiro CLI
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
Direzione di ricerca
No source file, failing test, or reproduction steps are identified. Start by reviewing the CLI's retry path around the reported "Service is busy" and retry warnings, using q doctor and q restart as the initial checks; done means determining whether the cause is client-side or service-side and documenting a confirmed mitigation.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Checks
- I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
- I have run
q doctorin the affected terminal session - I have run
q restartand replicated the issue again
Operating system
Linux 7.0.0-1011-aws - Ubuntu 24.04.4 LTS
Expected behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Actual behaviour
On 2026-09-21 (UTC) I am repeatedly hitting server-side throttling during
normal Kiro CLI chat. Messages seen:
Service is busy, retrying in 2s...
WARNING: Retry #2, retrying within 10.0s..
Service is busy, retrying in 4s...
Retries climb to #3 repeatedly — roughly 10+ times per hour.
Ruled out locally: network healthy (DNS resolves backend endpoints, pings
succeed), machine idle (load avg ~0.09, 18 GB RAM free), CLI version current
(2.21.2). The explicit "Service is busy" text points to backend
throttling/overload, not a client-side issue. Responses do eventually arrive
after the retries but are significantly delayed.
Asking whether there is a known regional/service-side capacity or throttling
issue, and how to mitigate.
Steps to reproduce
No response
Environment
<This will be visible to anyone. Do not include personal or sensitive information>
[q-details]
version = "2.21.2"
hash = "a4729fa233d8097438cb3dcb4c9c8d2f21cc82d9"
date = "2026-09-08T19:39:39.264567Z (13d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz"
total-cores = 4
memory = "30.97 GB"
[system-info.os.linux]
kernel_version = "7.0.0-1011-aws"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"
[environment]
cwd = "/persistent/vscode-workspace/lead-engine"
cli-path = "/persistent/vscode-workspace/lead-engine"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
terminal = "VSCode"
install-method = "unknown"
[env-vars]
PATH = "/home/USER/.local/bin:/usr/local/bin:/usr/lib/code-server/lib/vscode/bin/remote-cli:/home/USER/.local/bin:/usr/local/bin:/home/USER/.local/bin:/home/USER/.local/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 441
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aws/amazon-q-developer-cli
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
aws/amazon-q-developer-cli#3898 ·
-
bug: invalid JSON in agent-format.md `allowedTools` Examples block (JS `//` comments + unquoted `@builtin`) breaks copy-pasteForse già presa @ken-jo l’ha presa 114 giorni fa. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
aws/amazon-q-developer-cli#3851 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
aws/amazon-q-developer-cli#3316 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
aws/amazon-q-developer-cli#3023 · 2 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
aws/amazon-q-developer-cli#3927 ·
Tutte le issue di aws/amazon-q-developer-cli
Issue simili
-
llm translation
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
area: backend type: enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
armadavalor/WinKnife#6 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
5omeOtherGuy/phaseone#870 ·
I maintainer di solito rispondono entro 1 giorno
-
Write a support policyAperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 72/100
MattA-Official/vwmcp#20 ·