# 2026-04-29 — Daily Log## Dreaming Status (Apr 30 00:40 UTC update)- **Still broken**: No new dream events since Apr 27 11:31 UTC (~61h ago)- Pattern: Dreams fire once after a gap, then stop completely- Gateway has restarted multiple times (PIDs 263379, 371254, 2297563)- No error messages in journalctl — gateway running clean- Dreaming scheduler appears non-functional- Manual intervention may be needed (restart openclaw-gateway, check plugin config)## Gateway Restarts (Apr 28-29)- PID 1822221 died sometime Apr 28- PID 263379 started Apr 28 ~unknown- PID 371254 started Apr 29 00:28:16- PID 2297563 started Apr 29 17:40:10 (current)## Notes- Dreaming investigation ongoing — no solution found yet- System otherwise healthy, no user conversations## Apr 30 Status (as of 18:26 UTC)- Dreaming: RESUMED! 🎉 2 events at Apr 30 17:15:45 + 18:13:49 UTC after ~75h gap- events.jsonl: 21 lines (was 19) — 2 new events- Pattern: 2 events within 58 minutes (not single-shot)- Gateway PID 2297563 running ~23h, memory 1.7GB## Apr 30 18:26 UTC — DREAMING RESUMED! 🎉- 2 new dream events after ~75h gap: Apr 30 17:15:45 and 18:13:49 UTC- events.jsonl now 21 lines (was 19)- Directory timestamp updated to Apr 30 18:13- Pattern changed: now 2 events within 58 minutes instead of the usual single-shot- Gateway PID 2297563 still running, memory 1.7GB## May 1 07:01 UTC — Dreaming HEALTHY again!- 11 new events fired at 2026-05-01T07:00:01.598Z- events.jsonl: 32 lines (was 21)- New files: session-corpus/, daily-ingestion.json, phase-signals.json, session-ingestion.json- Pattern: all 11 events same timestamp — batch processing- Gateway PID 1710, uptime ~29h, memory 913MB