#Bug: managed dreaming cron could not be reconciled (cron service unavailable)

1 messages · Page 1 of 1 (latest)

slender pulsar
#

Bug: managed dreaming cron could not be reconciled (cron service unavailable) — persists through restarts and upgrades
Version: 2026.5.4 (issue started in 2026.4.26)
Symptom:
Dream diary entries stopped generating after upgrading from 2026.4.21 → 2026.4.26. The following error appears in the gateway error log on a ~2h recurring interval and has never cleared:
[plugins] memory-core: managed dreaming cron could not be reconciled (cron service unavailable).
What still works: Nightly promotion (dreaming promotion complete at 3am) — memory candidates are evaluated and applied to MEMORY.md normally.
What's broken: Dream diary (narrative LLM entries in DREAMS.md). Last successful diary entry was April 27, 2026.
What's been tried:
• Multiple full gateway restarts
• Dreaming toggled off → on via Control UI (hot reload confirmed in log)
• Upgraded through 2026.4.26, 2026.5.2, 2026.5.4
• openclaw cron list shows the dreaming job present with status ok, last run 13h ago
Config:
"dreaming": {
"enabled": true,
"model": "ollama/gemma4:26b"
}
allowModelOverride: true, allowedModels: ["ollama/gemma4:26b"] — model endpoint is reachable.
openclaw memory status output: Shows dreaming schedule, no "blocked" status reported.

sage glenBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

slender pulsar
#

The REM/diary generation capability is fully functional — manual invocation via openclaw memory rem-backfill successfully processed 41 historical files and wrote 41 entries to DREAMS.md. The bug is isolated to the managed cron reconciliation that schedules automatic REM runs; the underlying pipeline (LLM call, corpus processing, file writes) is unaffected.

bleak roost
#

@untold crane I'm also getting "cron service unavailable"

May 10 20:00:51 server node[908913]: 2026-05-10T20:00:51.323+00:00 [plugins] memory-core: managed dreaming cron could not be reconciled (cron service unavailable).

untold craneBOT
#

That specific warning is from memory-core failing to resolve the Gateway cron service from its plugin runtime context — not from the Ollama model path. So the model being reachable makes sense, and cron list showing the job present means the persisted cron store is probably okay.

Two useful details I found in current docs/source:

  • A related startup race was fixed in 2026.4.29 (#72841), but you’re on 2026.5.4 and still seeing it, so this may be a remaining edge case rather than the original bug.
  • openclaw memory status only reports blocked for the older “managed cron exists but heartbeat isn’t firing” case. Your “cron service unavailable” log is earlier/lower-level than that: memory-core can’t get the cron service object when it tries to reconcile.

I’d do these in order:

openclaw update
openclaw gateway restart
openclaw doctor --fix
openclaw memory status --deep --json
openclaw cron list --json

If it persists on the latest release, I’d file this as a GitHub issue with those two JSON outputs plus the log line: https://github.com/openclaw/openclaw/issues