openclaw - 💡(How to fix) Fix [Bug]: active-memory timeoutMs not enforced — runs 30-40s despite 5s config [1 comments, 2 participants]

Summary

The \ctive-memory\ plugin's \ imeoutMs\ configuration is not being enforced. Despite setting \ imeoutMs: 5000\ (5 seconds), the plugin consistently runs for 30-40 seconds before timing out, blocking chat replies.

Steps to Reproduce

1. Enable active-memory plugin with \ imeoutMs: 5000\
2. Send any message to the agent
3. Observe in logs that active-memory takes 30-40 seconds to complete

Expected Behavior

active-memory should timeout after 5 seconds (as configured) and not block the main reply.

Actual Behavior

active-memory runs for 30-40 seconds despite \ imeoutMs: 5000:

\
12:15:49 [plugins] active-memory: ... timeoutMs=5000 queryChars=1302 12:16:22 [plugins] active-memory: ... status=timeout elapsedMs=32330 summaryChars=0 \\

Second attempt: \
12:18:33 [plugins] active-memory: ... timeoutMs=5000 queryChars=1543 12:19:13 [plugins] active-memory: ... status=timeout elapsedMs=40266 summaryChars=0 \\

Environment

• OpenClaw version: 2026.4.20 (115f05d)
• OS: Windows_NT 10.0.26200 (x64)
• Node.js: v24.14.0
• Embedding model: doubao-embedding-vision (volcengine, domestic API)
• Recall model: stepfun/step-3.5-flash
• Memory index size: 123MB

Analysis

• The embedding search itself takes 6-12 seconds (verified via \memory_search\ tool)
• The sub-agent spawn + LLM processing adds additional overhead
• The total time far exceeds the configured \ imeoutMs\
• This appears to be a regression or unimplemented timeout enforcement

Related

• Similar to #69182 but more severe (30-40s vs 5s delay)
• Issue #69182 reports ~5s delay matching timeoutMs; our case shows timeoutMs is not enforced at all

Workaround

Disable active-memory plugin (\plugins.entries.active-memory.enabled: false). Memory search tools (\memory_search/ \memory_get) still work when called manually.