What broke in OpenClaw v2026.4.14?

All existing conversations across multiple models and surfaces started failing with generic UI errors due to repeated active-memory pre-reply timeouts hitting the 15-second limit.

How do you fix the OpenClaw 4.14 active memory timeout?

Disabling Active Memory immediately restores responsiveness, or roll back to v2026.4.12 which is the last known good version.

What causes OpenClaw active memory timeouts?

The Active Memory plugin's pre-reply path attempts semantic search queries that consistently exceed the 15-second timeout budget, returning zero summary characters.

Does the active memory timeout affect all models?

Yes, the regression affects conversations across multiple models and surfaces — it is not limited to any specific model provider.

Was the active memory timeout fixed?

Later versions addressed the issue, with v2026.5.2 moving cold-start grace behind an explicit setupGraceTimeoutMs config option.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-4-14-active-memory-timeout-all-conversations-fail

⚠ IssueWide OpenBugLive

OpenClaw v2026.4.14 Active Memory Timeout Regression Breaks All Existing Conversations Across Models

After upgrading from v2026.4.12 to v2026.4.14, all existing conversations across multiple models and surfaces fail with generic UI error. Gateway logs show repeated active-memory pre-reply timeouts hitting the 15s limit. Disabling Active Memory immediately restores responsiveness. Rollback to 4.12 is the only fix. Related issues cascade through 4.15 with 120s timeout chains.

Product Idea from this Signal

A runtime middleware that intercepts OpenClaw agent failures, reasoning leaks, memory timeouts, and processing stalls before they reach end users

446 ▲

OpenClaw agents fail in at least four distinct patterns that existing monitoring tools only detect after the damage is done. Internal reasoning text leaks into user-visible messages across Discord, Telegram, and WhatsApp (9+ open GitHub issues, recurring across versions). Active Memory timeouts kill all conversations after upgrades. Processing lanes stall for minutes with no automatic recovery. Codex runtime injects 30K tokens of overhead per turn making interactive use impossible. This middleware sits between the OpenClaw Gateway and channel outputs, pattern-matches known failure signatures in real time, and either suppresses the bad output (reasoning leaks), force-resets stuck lanes (stalls), or falls back to a cached last-good response (timeouts) before the user ever sees the error.

CLIOPEN-SOURCERELIABILITYMIDDLEWAREDEVTOOL

UnderservedView Opportunity →