Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Repeated Feishu tool registration logs and slower Feishu responses during a single startup [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#55530•Fetched 2026-04-08 01:38:26
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
wxfkuq2023wxfkuq2023
Participants
magicianymagicianywxfkuq2023wxfkuq2023
Timeline (top)
commented ×1labeled ×1

During a single startup, Feishu-related tools are registered multiple times in logs, and Feishu responses are slower than expected.

Root Cause

No direct evidence was collected showing that the issue was caused by the configured model itself.

Code Example

Observed repeated registrations during a single startup:

- `feishu_doc Registered ...`
- `feishu_chat Registered ...`
- `feishu_wiki Registered ...`
- `feishu_drive Registered ...`
- `feishu_bitable Registered ...`

These registration messages appeared more than once during the same startup.

A channel-ready message similar to:

- `OpenClaw China Channels 已就绪!`

also appeared repeatedly during the same startup.

Additional observed evidence from investigation:

- `plugins.allow` parsed correctly and was not actually empty.
- After correcting `openclaw.json` to strict JSON, the repeated initialization behavior was still observed.
- Temporarily disabling `openclaw-weixin` did not stop the repeated registrations.
- Temporarily disabling `wecom` did not stop the repeated registrations.
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

During a single startup, Feishu-related tools are registered multiple times in logs, and Feishu responses are slower than expected.

Steps to reproduce

  1. Start OpenClaw version 2026.3.24 with the Feishu channel enabled.
  2. Observe the startup logs.
  3. Check whether Feishu-related registrations such as feishu_doc, feishu_chat, feishu_wiki, feishu_drive, and feishu_bitable appear more than once during the same startup.
  4. Check whether the channel-ready log message is also printed repeatedly during the same startup.

Expected behavior

Each Feishu-related tool registration should appear once per startup, and the channel-ready message should not repeat during the same startup.

Actual behavior

During one observed startup, registrations for Feishu-related tools appeared multiple times in logs, including:

  • feishu_doc
  • feishu_chat
  • feishu_wiki
  • feishu_drive
  • feishu_bitable

A channel-ready log message similar to OpenClaw China Channels 已就绪! also appeared repeatedly during the same startup.

In the same environment, Feishu responses were observed to be slower than expected.

OpenClaw version

2026.3.24

Operating system

Linux 5.10.134-19.2.al8.x86_64

Install method

aliyun

Model

gpt-5.4

Provider / routing chain

cliproxyapi

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Observed repeated registrations during a single startup:

- `feishu_doc Registered ...`
- `feishu_chat Registered ...`
- `feishu_wiki Registered ...`
- `feishu_drive Registered ...`
- `feishu_bitable Registered ...`

These registration messages appeared more than once during the same startup.

A channel-ready message similar to:

- `OpenClaw China Channels 已就绪!`

also appeared repeatedly during the same startup.

Additional observed evidence from investigation:

- `plugins.allow` parsed correctly and was not actually empty.
- After correcting `openclaw.json` to strict JSON, the repeated initialization behavior was still observed.
- Temporarily disabling `openclaw-weixin` did not stop the repeated registrations.
- Temporarily disabling `wecom` did not stop the repeated registrations.

Impact and severity

  • Affected users/systems/channels: Feishu channel in the tested Linux environment.
  • Severity: Annoying to workflow.
  • Frequency: Observed in the tested startup(s).
  • Consequence: Repeated startup log output and slower Feishu responses.

Additional information

During investigation, the following were directly checked:

  • openclaw.json had a trailing comma removed and then passed strict JSON parsing.
  • plugins.allow parsed correctly and was not actually empty.
  • Disabling openclaw-weixin did not remove the repeated Feishu registrations.
  • Disabling wecom also did not remove the repeated Feishu registrations.

No direct evidence was collected showing that the issue was caused by the configured model itself.

extent analysis

Fix Plan

To address the issue of repeated Feishu-related tool registrations and slower responses, we will implement the following steps:

  • Step 1: Review and Refactor Registration Logic

    • Inspect the code responsible for registering Feishu-related tools.
    • Ensure that each tool is registered only once per startup.
    • Consider using a Set data structure to keep track of registered tools.

Example of using a Set to track registered tools

registered_tools = set()

def register_tool(tool_name): if tool_name not in registered_tools: # Register the tool print(f"{tool_name} Registered ...") registered_tools.add(tool_name)


*   **Step 2: Optimize Feishu Response Handling**
    *   Investigate the cause of slower Feishu responses.
    *   Consider implementing caching or optimizing database queries to improve response times.

    ```python
# Example of using caching to improve response times
import functools

@functools.lru_cache(maxsize=128)
def get_feishu_response(tool_name):
    # Simulate a slow response
    import time
    time.sleep(1)
    return f"Response from {tool_name}"
  • Step 3: Review Logging Configuration
    • Check the logging configuration to ensure that log messages are not being duplicated.
    • Consider setting up log rotation and retention policies to prevent log files from growing too large.

Verification

To verify that the fix worked:

  1. Start OpenClaw with the Feishu channel enabled.
  2. Observe the startup logs to ensure that each Feishu-related tool registration appears only once.
  3. Check the channel-ready log message to ensure it does not repeat during the same startup.
  4. Test Feishu responses to ensure they are no longer slower than expected.

Extra Tips

  • Regularly review and refactor code to prevent similar issues from arising in the future.
  • Consider implementing automated tests to catch registration and response issues before they reach production.
  • Monitor log files and system performance to quickly identify and address any potential problems.

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

Each Feishu-related tool registration should appear once per startup, and the channel-ready message should not repeat during the same startup.

#api#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

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

Back to top recommendations

TRENDING