openclaw - 💡(How to fix) Fix Bug: Dreaming session-corpus ingestion stopped — 175 sessions unprocessed since 5/15

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…

Session-corpus ingestion stopped processing new session transcripts after 2026-05-15. Dreaming cron runs daily and reports status: ok, but the session-ingestion.json state hasn't updated since 5/15, and 175 out of 177 sessions created after 5/15 are missing from seenMessages.

Root Cause

Root cause hypothesis

RAW_BUFFERClick to expand / collapse

Bug: Dreaming session-corpus ingestion stopped after 5/15 — 175 sessions unprocessed

Summary

Session-corpus ingestion stopped processing new session transcripts after 2026-05-15. Dreaming cron runs daily and reports status: ok, but the session-ingestion.json state hasn't updated since 5/15, and 175 out of 177 sessions created after 5/15 are missing from seenMessages.

Evidence

Session-corpus frozen:

  • Latest corpus file: 2026-05-15.txt (425 bytes), nothing after 5/15
  • session-ingestion.json last modified: 2026-05-15 03:02
  • Tracked files: 352 (all pre-5/15)

Sessions vs ingestion:

  • Total session .jsonl files: 466
  • Sessions created after 5/15: 177
  • After-5/15 sessions NOT in seenMessages: 175
  • Even the current active conversation session (9 user messages) is missing

Dreaming cron still runs:

  • Job 36bce6b8 "Memory Dreaming Promotion" runs daily at 3:00 AM, all status: ok
  • Recent summaries: all NO_REPLY (1-5 second duration, effectively no-op)
  • DREAMS.md last updated: 5/15

What's NOT broken:

  • memory-core plugin enabled, dreaming enabled
  • openclaw memory status --deep reports healthy (except 12 invalid recall entries — likely stale)
  • Recall store: 8690 entries still functional
  • Session files exist at ~/.openclaw/agents/main/sessions/*.jsonl
  • listSessionFilesForAgent("main") returns correct files

Root cause hypothesis

The ingestion state (session-ingestion.json) has seenMessages with 1592 scopes but new sessions are never added. The collectSessionIngestionBatches function correctly enumerates session files but something in the ingestion loop prevents new sessions from being processed or the state from being persisted.

The ingestion state key format is main:sessions/main/{uuid}.jsonl — the /main/ part is the agentId (not a subdirectory), and the actual files are at ~/.openclaw/agents/main/sessions/{uuid}.jsonl. This pattern worked before 5/15, so it's likely a regression.

Version

OpenClaw 2026.5.20 (e510042), Linux WSL2

Impact

No new session content flows into Dreaming phases. No new DREAMS.md entries since 5/15.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING