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 enabledopenclaw 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.
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 thesession-ingestion.jsonstate hasn't updated since 5/15, and 175 out of 177 sessions created after 5/15 are missing fromseenMessages.Evidence
Session-corpus frozen:
2026-05-15.txt(425 bytes), nothing after 5/15session-ingestion.jsonlast modified: 2026-05-15 03:02Sessions vs ingestion:
.jsonlfiles: 466seenMessages: 175Dreaming cron still runs:
36bce6b8"Memory Dreaming Promotion" runs daily at 3:00 AM, allstatus: okNO_REPLY(1-5 second duration, effectively no-op)What's NOT broken:
memory-coreplugin enabled, dreaming enabledopenclaw memory status --deepreports healthy (except 12 invalid recall entries — likely stale)Recall store: 8690 entriesstill functional~/.openclaw/agents/main/sessions/*.jsonllistSessionFilesForAgent("main")returns correct filesRoot cause hypothesis
The ingestion state (
session-ingestion.json) hasseenMessageswith 1592 scopes but new sessions are never added. ThecollectSessionIngestionBatchesfunction 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.