#pipeline-error
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2544 issues
Every agent response via Claude models (MyClaw provider) triggers an `Unexpected event order, got message_start before receiving "message_stop"` error that is displayed as a visible error message in the Telegram chat. This makes the chat essentially unusable — every reply from the agent is followed by a red error notification. **Affects all Claude models tested** (claude-opus-4.6 and claude-sonnet-4.6). Not yet tested on non-Claude models.
Feishu (飞书) channel cannot send messages when system HTTP proxy is configured. Error: `Cannot destructure property 'tenant_access_token' of '(intermediate value)' as it is undefined.` **Root cause:** The `@larksuiteoapi/node-sdk` uses axios which respects system proxy settings (`http_proxy`/`https_proxy`). When proxy is enabled (e.g., v2rayN), requests to `open.feishu.cn` are routed through the proxy and fail with HTTP 400 error: `"The plain HTTP request was sent to HTTPS port"`.
Run >crewai install error Resolved 149 packages in 107ms error: Distribution `lancedb==0.30.1 @ registry+https://pypi.org/simple` can't be installed because it doesn't have a source distribution or wheel for the current platform hint: You're on Windows (`win_amd64`), but `lancedb` (v0.30.1) only has wheels for the following platforms: `manylinux_2_17_aarch64`, `manylinux_2_28_aarch64`, `manylinux_2_28_x86_64`, `manylinux2014_aarch64`, `macosx_11_0_arm64`; consider adding "sys_platform == 'win32' and platform_machine == 'AMD64'" to `tool.uv.required-environments` to ensure uv resolves to a version with compatible wheels An error occurred while running the crew: Command '['uv', 'sync']' returned non-zero exit status 2.
Add configuration to disable external model pricing data fetching during Gateway startup.
When the primary model (OpenAI Codex / ChatGPT Plus OAuth) hits the ChatGPT Plus subscription usage cap, OpenClaw: 1. **Surfaces the error to the UI** even when a fallback model (Anthropic) successfully handles the request 2. **Labels the error as "API rate limit reached"** — misleading when on OAuth (not an API key). The actual failure is a ChatGPT Plus plan usage cap, which is a different condition entirely. 3. **Triggers a WebSocket auth lockout loop** when the user attempts reconnect after a gateway restart, compounding the perceived outage.
Environment | Component | Value | | ---------------- | ------------- | | OS | Windows 10/11 | | OpenClaw Version | 2026.4.1 | | Node.js | v25.7.0 | | Platform | win32 (x64) | ─── Description On Windows, even with security: standard and allowFrom configured, OpenClaw requires explicit approval for every command executed via Telegram. This makes remote management impractical. ─── Configuration { "security": "standard", "channels": { "telegram": { "enabled": true, "dmPolicy": "allowlist", "allowFrom": ["<telegram_user_id>"] } } } ─── Error Message Warning: allowlist auto-execution is unavailable on win32; explicit approval is required. Root Cause The restriction appears to be hardcoded: allowlist auto-execution is unavailable on win32; explicit approval is required ─── Impact • Remote management is impractical on Windows • Every command requires explicit approval • Telegram bot utility is severely limited ─── Suggested Fix
All CLI commands (cron, config, doctor, etc.) fail to connect to the gateway via WebSocket with handshake timeout. The gateway itself runs normally - channel messaging (Feishu) and browser dashboard both work. Only CLI-gateway RPC connections are broken.
qmd版本2.0.1，openclaw版本20260401.集成qmd后运行报错qmd boot update failed: Error: qmd update failed (code 1): file:///C:/software/nvm/v25.8.2/node_modules/@tobilu/qmd/bin/qmd:2 # Resolve symlinks so global installs (npm link / npm install -g) can find the ^
在 Windows 上执行安装脚本，配置好模型后到下一步时报错：Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]。
When `gateway.auth.token` is migrated from plaintext config to a SecretRef, the Browser Relay server still works, but the Chrome/Brave extension setup flow becomes incomplete. The relay auth path can resolve `gateway.auth.token` from SecretRefs, but the browser extension still expects a literal plaintext token in its own local storage (`chrome.storage.local.gatewayToken`). After hardening gateway auth to use a SecretRef, the extension prompts for a token and cannot discover it through first-party setup.
After restarting the openclaw gateway (any reason: config change, system reboot, manual restart), **all HTTP requests return `500 Internal Server Error`**. WebSocket connections continue to work normally. The root cause is a module resolution failure for `@slack/web-api` that is silently swallowed by a bare `catch {}` block. ---
The WhatsApp health monitor's `stale-socket` restart cycle reliably re-establishes the **personal/inbound listener** but silently fails to reconnect the **Web listener** (used for all proactive outbound sends). This causes all outbound WhatsApp messaging — cron deliveries, `message` tool sends, announce-mode delivery — to fail with: ``` No active WhatsApp Web listener (account: default). Start the gateway, then link WhatsApp with: openclaw channels login --channel whatsapp --account default. ``` Meanwhile, inbound DMs continue to work normally (personal listener is fine), masking the failure.
Gateway 访问飞书 API（`open.feishu.cn`）反复超时（10s），但用户本地网络直连飞书服务器正常。