openclaw - ✅(Solved) Fix [Bug]: channels.feishu: invalid config: must NOT have additional properties [1 pull requests, 6 comments, 6 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#56883Fetched 2026-04-08 01:46:30
View on GitHub
Comments
6
Participants
6
Timeline
14
Reactions
0
Author
Timeline (top)
commented ×6cross-referenced ×4labeled ×2closed ×1

After upgrading from 3.24 to 3.28, the gateway failed to start up. openclaw doctor --fix says: Invalid config: channels.feishu: invalid config: must NOT have additional properties How can this issue be fixed?

Root Cause

After upgrading from 3.24 to 3.28, the gateway failed to start up. openclaw doctor --fix says: Invalid config: channels.feishu: invalid config: must NOT have additional properties How can this issue be fixed?

Fix Action

Fixed

PR fix notes

PR #56893: fix: stop bundled Feishu schema from rejecting valid plugin config

Description (problem / solution / changelog)

Summary

  • make the bundled Feishu channel config schema permissive instead of rejecting unknown keys up front
  • defer validation to the Feishu plugin's runtime schema, which already knows the real supported fields

Why

The bundled metadata currently exposes an empty strict object, so core startup validation rejects valid Feishu options like footer.elapsed / footer.status before the plugin can parse them. Making the bundled schema permissive restores compatibility with the plugin's actual config surface.

Closes #56882 Closes #56883

Changed files

  • extensions/feishu/openclaw.plugin.json (modified, +1/-2)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 3.24 to 3.28, the gateway failed to start up. openclaw doctor --fix says: Invalid config: channels.feishu: invalid config: must NOT have additional properties How can this issue be fixed?

Steps to reproduce

tried to roll back to the 3.24 version (openclaw update --tag 2026.3.24), failed too with the following message: Config invalid File: ~/.openclaw/openclaw.json Problem:

  • channels.feishu: invalid config: must NOT have additional properties

Expected behavior

the config works in 3.24

Actual behavior

failed to start up

OpenClaw version

3.28

Operating system

ubuntu24

Install method

No response

Model

minimax

Provider / routing chain

minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves removing additional properties from the channels.feishu configuration in the ~/.openclaw/openclaw.json file.

  • Open the ~/.openclaw/openclaw.json file in a text editor.
  • Locate the channels.feishu section and remove any properties that are not recognized by the OpenClaw 3.28 configuration schema.
  • Example of invalid configuration:
"channels": {
  "feishu": {
    "property1": "value1",
    "property2": "value2", // remove this line if property2 is not a valid property
    "validProperty": "validValue"
  }
}
  • Example of valid configuration:
"channels": {
  "feishu": {
    "validProperty": "validValue"
  }
}
  • Save the changes to the ~/.openclaw/openclaw.json file.

Verification

To verify that the fix worked, try starting the OpenClaw gateway again. If the configuration is valid, the gateway should start up successfully.

Extra Tips

  • Make sure to check the OpenClaw documentation for the 3.28 version to ensure that the channels.feishu configuration is valid and up-to-date.
  • If you are still experiencing issues, try running openclaw doctor --fix again to see if there are any other configuration errors that need to be addressed.

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

the config works in 3.24

Still need to ship something?

×6

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

Back to top recommendations

TRENDING