Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Dreaming config: `timezone` field rejected by schema despite being shown in docs [1 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#62515•Fetched 2026-04-08 03:03:14
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
PrinceOfEgyptPrinceOfEgypt
Participants
PrinceOfEgyptPrinceOfEgypt

The official documentation for Memory Dreaming shows timezone as a valid config field under plugins.entries.memory-core.config.dreaming:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "timezone": "America/Los_Angeles",
            "frequency": "0 */6 * * *"
          }
        }
      }
    }
  }
}

However, applying this config via config.patch (or config.apply) in v2026.4.5 produces a validation error:

invalid config: plugins.entries.memory-core.config.dreaming: invalid config: must NOT have additional properties

Error Message

However, applying this config via config.patch (or config.apply) in v2026.4.5 produces a validation error: Users following the docs example will get a hard config validation error. The timezone field appears intentional (it's shown in the docs quick-start example), suggesting either:

Root Cause

The official documentation for Memory Dreaming shows timezone as a valid config field under plugins.entries.memory-core.config.dreaming:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "timezone": "America/Los_Angeles",
            "frequency": "0 */6 * * *"
          }
        }
      }
    }
  }
}

However, applying this config via config.patch (or config.apply) in v2026.4.5 produces a validation error:

invalid config: plugins.entries.memory-core.config.dreaming: invalid config: must NOT have additional properties

Fix Action

Workaround

Use a UTC-equivalent cron expression in frequency (e.g. "0 8 * * *" for 3 AM CDT). This works but is fragile across DST changes.

Code Example

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "timezone": "America/Los_Angeles",
            "frequency": "0 */6 * * *"
          }
        }
      }
    }
  }
}

---

invalid config: plugins.entries.memory-core.config.dreaming: invalid config: must NOT have additional properties
RAW_BUFFERClick to expand / collapse

Summary

The official documentation for Memory Dreaming shows timezone as a valid config field under plugins.entries.memory-core.config.dreaming:

{
  "plugins": {
    "entries": {
      "memory-core": {
        "config": {
          "dreaming": {
            "enabled": true,
            "timezone": "America/Los_Angeles",
            "frequency": "0 */6 * * *"
          }
        }
      }
    }
  }
}

However, applying this config via config.patch (or config.apply) in v2026.4.5 produces a validation error:

invalid config: plugins.entries.memory-core.config.dreaming: invalid config: must NOT have additional properties

Schema inspection

Running config.schema.lookup on plugins.entries.memory-core.config.dreaming confirms only two children are defined:

  • enabled (boolean)
  • frequency (string)

timezone is not present, and additionalProperties: false causes the rejection.

Impact

Users following the docs example will get a hard config validation error. The timezone field appears intentional (it's shown in the docs quick-start example), suggesting either:

  1. The schema was not updated to include timezone before v2026.4.5 shipped, or
  2. The docs were written ahead of the implementation

Workaround

Use a UTC-equivalent cron expression in frequency (e.g. "0 8 * * *" for 3 AM CDT). This works but is fragile across DST changes.

Expected behavior

timezone should be accepted as a valid field alongside enabled and frequency, consistent with the documentation.

Version

OpenClaw v2026.4.5

extent analysis

TL;DR

Update the schema to include the timezone field or wait for an official fix, as the current version does not support it despite being documented.

Guidance

  • Verify the schema definition for plugins.entries.memory-core.config.dreaming to confirm that timezone is not included.
  • Consider using a temporary workaround by setting the frequency to a UTC-equivalent cron expression, but be aware that this may not account for daylight saving time (DST) changes.
  • Review the documentation and version history to determine if the timezone field was intended for a future release or if it was an oversight.
  • Check for any updates or patches to OpenClaw v2026.4.5 that may address this issue.

Example

No code example is provided as the issue is related to configuration and schema validation rather than code implementation.

Notes

The provided information suggests that the issue is due to a mismatch between the documented configuration and the actual schema validation in OpenClaw v2026.4.5. Without further information or updates, it's uncertain when or if the timezone field will be officially supported.

Recommendation

Apply workaround: Use a UTC-equivalent cron expression in frequency as a temporary solution until an official fix or update is available that includes support for the timezone field. This recommendation is based on the need for a functional, albeit imperfect, solution given the current version's limitations.

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…

FAQ

Expected behavior

timezone should be accepted as a valid field alongside enabled and frequency, consistent with the documentation.

#pipeline error#runtime error#dependency conflict#environment setup#docker 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