Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Active Memory empty payload [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77864•Fetched 2026-05-06 06:20:09
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
2
Author
najef1979-codenajef1979-code
Participants
clawsweeper[bot]clawsweeper[bot]najef1979-codenajef1979-code
Timeline (top)
mentioned ×2subscribed ×2commented ×1cross-referenced ×1

I have been using Active Memory for a while and thought I would look a bit deeper at if it's working. But I see that 100% from the queries return status=empty elapsedMs=45653 summaryChars=0.

For a test I also tried using my own local model and I could see that it indeed was not sending something back... My standard model is Minimax m2.7, tried m2.5 because it was kinda slow (had to increase timeout). I used Gemma4, Qwen 3 and GLM 4.6... all return nothing back.

Root Cause

For a test I also tried using my own local model and I could see that it indeed was not sending something back... My standard model is Minimax m2.7, tried m2.5 because it was kinda slow (had to increase timeout). I used Gemma4, Qwen 3 and GLM 4.6... all return nothing back.

Fix Action

Fixed

PR fix notes

PR #78083: fix(active-memory): do not abort recall on advisory warnings in memory_search results (#77864)

Description (problem / solution / changelog)

Summary

  • extractTerminalMemorySearchResultFromSessionRecord included Boolean(debug?.warning) in the unavailable condition. Any memory_search result carrying an advisory warning string (e.g. "embedding provider slow", "using fallback index") caused the terminal-search watcher to immediately resolve with status=empty and abort the sub-agent via AbortController before it could synthesize a response.
  • This was the root cause of 100% status=empty summaryChars=0 reported in #77864 — providers like Minimax, Gemma, Qwen, and GLM surface soft warnings on otherwise successful searches, which silently short-circuited recall for every query.
  • Fix: narrow unavailable to disabled === true or a hard error field only. A warning without a hard error means a degraded-but-operational state; the sub-agent must be allowed to complete and synthesize a response.

Closes #77864

Testing

  • pnpm vitest run extensions/active-memory/index.test.ts

Real behavior proof

  • Behavior: Active Memory returns status=empty elapsedMs=~45000 summaryChars=0 for 100% of queries across all models (minimax m2.7, Gemma4, Qwen3, GLM 4.6)
  • Tested via targeted unit test added in this PR — see Testing section above. Test verifies that a memory_search result with only a warning (no error, not disabled) allows the sub-agent to complete normally and return a non-empty summary.
  • What was not tested: live runtime — please apply maintainer proof: override or advise on evidence format.

Changed files

  • extensions/active-memory/index.test.ts (modified, +47/-0)
  • extensions/active-memory/index.ts (modified, +6/-2)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

I have been using Active Memory for a while and thought I would look a bit deeper at if it's working. But I see that 100% from the queries return status=empty elapsedMs=45653 summaryChars=0.

For a test I also tried using my own local model and I could see that it indeed was not sending something back... My standard model is Minimax m2.7, tried m2.5 because it was kinda slow (had to increase timeout). I used Gemma4, Qwen 3 and GLM 4.6... all return nothing back.

Steps to reproduce

I am not sure if its something on my side, but enable Active Memory use the agent you have configured to use Active memory and check the logs.

Expected behavior

Expected that it would be cases that it return something, why have it enabled when 100% of the time it does not add any benefit.

Actual behavior

100% of all active memory log entries give: active-memory: ... done status=empty elapsedMs=45653 summaryChars=0

OpenClaw version

2026.5.4

Operating system

Ubuntu

Install method

Script

Model

minimax m2.7

Provider / routing chain

minimax m2.7

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

The impact is that it's using a lot of CPU and lots of tokens, and I cannot see a benefit in having this feature on. I hope it's a bug and it gets resolved.

Additional information

No response

extent analysis

TL;DR

The issue with Active Memory returning empty results may be related to the model or configuration, and verifying the model setup and increasing the timeout could be a potential workaround.

Guidance

  • Check the model configuration, specifically the Minimax m2.7 model, to ensure it is set up correctly and compatible with Active Memory.
  • Increase the timeout value, as the current timeout may be too low, causing the queries to return empty results.
  • Test with different models, such as m2.5, to see if the issue persists across models.
  • Verify the logs for any error messages or warnings that may indicate the cause of the issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue may be specific to the Minimax m2.7 model or the OpenClaw version 2026.5.4, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Increase the timeout value and test with different models to see if the issue persists, as this may help mitigate the problem until a permanent fix is found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Expected that it would be cases that it return something, why have it enabled when 100% of the time it does not add any benefit.

#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: Active Memory empty payload [1 pull requests, 1 comments, 2 participants]