#cache-issue
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2570 issues
`gateway/model-pricing` repeatedly logs: `pricing bootstrap failed: TimeoutError: The operation was aborted due to timeout` This happens frequently on startup/runtime, but there appears to be no config flag or env var to disable model-pricing bootstrap when pricing is non-critical.
Setting `ask: off` / `security: full` in exec-approvals.json has no effect on Windows; every exec call returns `exec denied: allowlist miss` even after gateway restart.
After re-authenticating OpenAI Codex multiple times, Gateway kept logging `refresh_token_reused` and some runs failed with OAuth refresh errors. In our case, the root cause appears to be that the main agent auth store retained both: - `openai-codex:default` (older login) - a newer named Codex profile (email-based profile key) Different paths seemed to use different profiles, which led to refresh-token rotation conflicts. Removing the stale `openai-codex:default` entry and keeping only the newest named profile fixed the issue.
When routing Azure GPT-5.2 chat requests through LiteLLM, `vector_store_ids` can leak into provider payload via `extra_body`, causing Azure to reject the request with: `litellm.BadRequestError: AzureException BadRequestError - Unknown parameter: 'vector_store_ids'`
The Claude desktop app opens but the main content area is completely blank/black. Only the left sidebar renders. The issue started after an automatic update.
# OpenClaw Cron 调度时间偏移严重，执行时间记录不准确
`openclaw doctor` reports `Telegram: not configured` in the channel probe section, even though the Telegram channel is fully operational.
`github_copilot/gpt-5.4` is not accessible via the `/chat/completions` endpoint on the GitHub Copilot API. When a request is sent through the LiteLLM proxy (via the Anthropic `/v1/messages` pass-through endpoint), it always routes through `litellm.acompletion()` → `/chat/completions`, which GitHub Copilot rejects with: ``` model "gpt-5.4" is not accessible via the /chat/completions endpoint code: unsupported_api_for_model ```
When re-authenticating the Qwen model, it shows authentication successful but the terminal still running starting Qwen OAuth.
The gateway's Telegram client enters an unrecoverable state after a transient network hiccup. Once it fails, it retries `sendChatAction` in a tight loop (~every 3 seconds) indefinitely, even across gateway restarts.