Summary
memory-core managed dreaming appears to complete the actual work, but narrative session cleanup fails because it requires operator.admin.
Observed behavior
From gateway logs after update to 2026.4.21:
- memory-core: dream diary entry written for light phase
- memory-core: dream diary entry written for rem phase
- memory-core: normalized recall artifacts before dreaming (rewrote recall store)
- memory-core: dreaming promotion complete (workspaces=2, candidates=0, applied=0, failed=0)
- memory-core: narrative session cleanup failed for light phase: missing scope: operator.admin
- memory-core: narrative session cleanup failed for rem phase: missing scope: operator.admin
Also, the managed cron itself is present and healthy:
- job exists: Memory Dreaming Promotion
- enabled: true
- lastRunStatus: ok
- consecutiveErrors: 0
Why this seems like a product issue
This does not look like a user misconfiguration:
- the scheduled dreaming job runs successfully
- the diary/promote path succeeds
- only cleanup fails
- the required scope (operator.admin) is not something a normal user/session can realistically satisfy in common installs
So this looks like one of:
- cleanup should not require operator.admin, or
- cleanup should degrade gracefully / skip silently when that scope is unavailable instead of logging repeated failure messages
Expected behavior
If the main dreaming/promotion path succeeds, cleanup should either:
- run without elevated admin-only scope, or
- no-op cleanly when privileges are insufficient
Environment
- OpenClaw stable 2026.4.21
- Gateway running locally on Windows
- Managed cron job for memory-core short-term promotion enabled and healthy
If helpful, I can provide a fuller log excerpt, but the lines above capture the failure mode clearly.
Summary
memory-core managed dreaming appears to complete the actual work, but narrative session cleanup fails because it requires operator.admin.
Observed behavior
From gateway logs after update to 2026.4.21:
Also, the managed cron itself is present and healthy:
Why this seems like a product issue
This does not look like a user misconfiguration:
So this looks like one of:
Expected behavior
If the main dreaming/promotion path succeeds, cleanup should either:
Environment
If helpful, I can provide a fuller log excerpt, but the lines above capture the failure mode clearly.