#batch-processing
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2572 issues
On the same Ubuntu VPS and openai-codex OAuth setup, OpenClaw 2026.4.9 fails to return runtime chat replies in Control UI, WhatsApp, and WeCom, while 2026.3.28 works.
After upgrated to 2026.4.1, the gateway display the following message after input some message in openclaw webpage: 17:48:38+08:00 [agent/embedded] embedded run failover decision: runId=fa92620f-4ad8-40d4-9855-9f82a5d42ac8 stage=assistant decision=surface_error reason=timeout provider=custom-127-0-0-1-8088/NVIDIA-Nemotron-3-Super-120B-A12B profile=- ... and then the LLM running is idle, the openclaw stopped working.
After upgrading to OpenClaw 2026.3.13 on Windows, the ACP runtime backend is unavailable. This appears to be a recurrence of #43997, but with two compounding issues specific to Windows.
OpenClaw aborts requests after about 1 minute with Request timed out before a response was generated even though agents.defaults.timeoutSeconds is set to 18 minutes. <img width="1050" height="537" alt="Image" src="https://github.com/user-attachments/assets/963947c8-09cf-4902-88f4-76ea46eb40e4" />
When running a single gateway with multiple Telegram bot accounts (8 in our case), the gateway produces persistent `409 Conflict` errors on `getUpdates` — even though every account has a **unique bot token**.
Allow vault/exec secret references (e.g. OpenBao, HashiCorp Vault) to be used as the `apiKey` source in `auth.profiles`, the same way they are already supported in `tools`, `channels`, `gateway`, `skills`, and `messages`.
When upgrading from 2026.3.24 to 2026.3.28, Gateway refuses to start with: ``` channels.feishu: invalid config: must NOT have additional properties channels.feishu.accounts.jeeves: invalid config: must NOT have additional properties channels.feishu.accounts.ivy: invalid config: must NOT have additional properties channels.feishu.accounts.crichton: invalid config: must NOT have additional properties channels.feishu.accounts.marple: invalid config: must NOT have additional properties ``` The external plugin `@larksuite/openclaw-lark` (2026.3.26) registers channel id `feishu` with a full config schema that includes keys like `replyMode`, `footer`, `botName`, `blockStreaming`, `markdown`, `dedup`, `threadSession`, and `uat`. However, the bundled `@openclaw/feishu` plugin also registers channel id `feishu` with a `channelConfigs` schema (new in 2026.3.28) that does **not** include these keys and sets `additionalProperties: false`. The bundled plugin is explicitly disabled (`plugins.entries.feishu.enabled: false`), but its schema still takes priority during config validation.
When Openclaw uses bc for calculation, the TUI output will omit duplicate number, but get normal when reopen the TUI
`task-manager` workers can resolve `SKILL.md` from the bundled OpenClaw install path instead of the current workspace path, which causes startup to fail with `ENOENT`.
Running openclaw gateway probe returns "Connect: failed - timeout" even though the gateway is fully functional (HTTP works, WebSocket connections work). Environment: OpenClaw: 2026.3.13 OS: Linux 6.12.62+rpt-rpi-2712 (arm64) - Raspberry Pi 5 Gateway: loopback (127.0.0.1:18789) Steps to reproduce:
`openclaw doctor --fix` does not fully migrate legacy cron metadata when a job still has top-level `notify: true` and `cron.webhook` is unset. Observed behavior: - Doctor reports legacy cron storage and warns about `notify: true` fallback. - Running `openclaw doctor --fix` prints `Cron store normalized at ~/.openclaw/cron/jobs.json.` - But the same legacy warning persists on subsequent doctor runs until the user manually edits `jobs.json` and removes `notify`. This creates a confusing loop where doctor claims normalization succeeded, but legacy state remains.