Summary
Active Memory plugin consistently times out on every run since upgrading to v2026.4.26 (also occurred on v2026.4.25). The plugin starts, hits the 15s timeout, returns 0 summary chars, and the embedded run fails over with surface_error.
Related issues: #68825, #66708, #66157, #65159
Environment
- OpenClaw: 2026.4.26 (upgraded from 2026.4.25)
- OS: macOS 26.4.1 (arm64) Mac Mini M4
- Node: 25.8.1
- Plugin compatibility: none
Active Memory Config
{
"active-memory": {
"enabled": true,
"config": {
"enabled": true,
"agents": ["telegram-chat"],
"allowedChatTypes": ["direct"],
"model": "openrouter/google/gemini-2.5-flash-lite",
"queryMode": "recent",
"promptStyle": "recall-heavy",
"timeoutMs": 15000,
"maxSummaryChars": 220
}
}
}
Reproduction
- Enable Active Memory plugin with OpenRouter as provider
- Send any message via Telegram
- Every active-memory run times out at 15s with 0 summary chars
Log Evidence
active-memory: agent=telegram-chat session=agent:telegram-chat:main activeProvider=openrouter activeModel=google/gemini-2.5-flash-lite start timeoutMs=15000 queryChars=926
active-memory: agent=telegram-chat session=agent:telegram-chat:main activeProvider=openrouter activeModel=google/gemini-2.5-flash-lite done status=timeout elapsedMs=15004 summaryChars=0
embedded_run_failover_decision: failoverReason=timeout provider=openrouter model=google/gemini-2.5-flash-lite timedOut=true aborted=true
Key Observations
- OpenRouter API itself works fine — direct curl to the same model returns in ~0.6s
- The timeout is in the plugin layer, not the API
openclaw status shows Plugin compatibility: none — may be related
- Memory search (memorySearch) works perfectly — only active-memory plugin is affected
- Issue persists across gateway restarts
- Channels table in
openclaw status is also empty (channels work fine via openclaw channels status)
Workaround
Disabling active-memory resolves the timeout, but removes automatic memory surfacing.
Full Status Output
Plugin compatibility: none
Memory: 965 files · 2609 chunks · sources memory · plugin memory-core · vector ready · fts ready · cache on (6290)
``
Summary
Active Memory plugin consistently times out on every run since upgrading to v2026.4.26 (also occurred on v2026.4.25). The plugin starts, hits the 15s timeout, returns 0 summary chars, and the embedded run fails over with
surface_error.Related issues: #68825, #66708, #66157, #65159
Environment
Active Memory Config
{ "active-memory": { "enabled": true, "config": { "enabled": true, "agents": ["telegram-chat"], "allowedChatTypes": ["direct"], "model": "openrouter/google/gemini-2.5-flash-lite", "queryMode": "recent", "promptStyle": "recall-heavy", "timeoutMs": 15000, "maxSummaryChars": 220 } } }Reproduction
Log Evidence
Key Observations
openclaw statusshowsPlugin compatibility: none— may be relatedopenclaw statusis also empty (channels work fine viaopenclaw channels status)Workaround
Disabling active-memory resolves the timeout, but removes automatic memory surfacing.
Full Status Output