Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [memory-core] "managed dreaming cron could not be reconciled (cron service unavailable)" startup race warning [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75889•Fetched 2026-05-02 05:28:24
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Author
highfly-hihighfly-hi
Participants
clawsweeper[bot]clawsweeper[bot]highfly-hihighfly-hi
Timeline (top)
commented ×1

Code Example

memory-core: managed dreaming cron could not be reconciled (cron service unavailable)

---

journalctl --user -u openclaw-<profile>-gateway.service -n 200 | grep "memory-core"
RAW_BUFFERClick to expand / collapse

[memory-core] "managed dreaming cron could not be reconciled (cron service unavailable)" startup race warning

Environment

  • openclaw 2026.4.29
  • memory-core plugin with dreaming.enabled: true
  • External cron via ~/.openclaw-secretary/cron/jobs.json works correctly (job Memory Dreaming Promotion id=90f6cecb…, schedule 0 3 * * *, last run status=ok 12.2s)

Symptom

On every gateway startup the log emits:

memory-core: managed dreaming cron could not be reconciled (cron service unavailable)

The warning is harmless — the cron does run on schedule via the external cron/jobs.json reconciliation that initializes after memory-core. But the noise:

  1. Hides real issues during startup log review.
  2. Misleads operators into thinking dreaming is broken (it isn't).
  3. Suggests memory-core queries the cron service before the cron plugin's croner module has finished registering.

Proposed fix

  • memory-core should defer cron reconciliation until the cron plugin signals ready (e.g., await gateway.plugins.waitFor('cron') or subscribe to a plugin:ready:cron event).
  • Alternatively, downgrade the message to info level and add a one-shot retry on next event-loop tick.

Repro

  1. Enable plugins.entries.memory-core.config.dreaming.enabled = true.
  2. Restart gateway, grep first 5 seconds of logs: 
    journalctl --user -u openclaw-<profile>-gateway.service -n 200 | grep "memory-core"
  3. Observe the warning, then verify via cron/jobs.json that the dreaming cron actually executes on schedule.

extent analysis

TL;DR

Defer cron reconciliation in memory-core until the cron plugin signals ready to resolve the startup race warning.

Guidance

  • Review the memory-core plugin code to determine the best approach for deferring cron reconciliation, such as using gateway.plugins.waitFor('cron') or subscribing to a plugin:ready:cron event.
  • Consider downgrading the message to info level and adding a one-shot retry on the next event-loop tick as an alternative solution.
  • Verify that the cron plugin's croner module has finished registering before attempting to reconcile the cron service.
  • Test the proposed fix by reproducing the issue using the provided repro steps and verifying that the warning is no longer emitted.

Example

// Example of deferring cron reconciliation using gateway.plugins.waitFor('cron')
gateway.plugins.waitFor('cron').then(() => {
  // Reconcile cron service here
});

Notes

The proposed fix assumes that the cron plugin emits a ready signal or event that can be awaited or subscribed to. If this is not the case, an alternative approach may be necessary.

Recommendation

Apply the proposed fix by deferring cron reconciliation in memory-core until the cron plugin signals ready, as this approach directly addresses the root cause of the issue and provides a clean solution.

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…
#callback error#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [memory-core] "managed dreaming cron could not be reconciled (cron service unavailable)" startup race warning [1 comments, 2 participants]