Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Frequent Service is busy / retry warnings in Kiro CLI

オープン
  • 何か問題がありますか？
#3,913 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
linux, rust
領域
backend, cli

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

Checks
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"
主要言語
Rust
スター
2k
フォーク
441
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aws/amazon-q-developer-cli のほかの issue

aws/amazon-q-developer-cli の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。