openclaw - 💡(How to fix) Fix [Bug]: Feishu API requests timeout repeatedly despite normal network connectivity to open.feishu.cn [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#61971Fetched 2026-04-08 03:10:35
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×2closed ×1

Gateway 访问飞书 API(open.feishu.cn)反复超时(10s),但用户本地网络直连飞书服务器正常。

Error Message

AxiosError: timeout of 10000ms exceeded

Root Cause

Gateway 访问飞书 API(open.feishu.cn)反复超时(10s),但用户本地网络直连飞书服务器正常。

Fix Action

Fix / Workaround

AxiosError: timeout of 10000ms exceeded at onChartStreamTimeout (node_modules/axios/index.cjs:?:?) at Object.dispatch (node_modules/axios/index.cjs:?:?) at短路 at AdjustedPassThrough.end (node_modules/axios/index.cjs:?:?) ]

Code Example

AxiosError: timeout of 10000ms exceeded

---

### 典型错误日志(已脱敏)


[error]: [
  AxiosError: timeout of 10000ms exceeded
  at onChartStreamTimeout (node_modules/axios/index.cjs:?:?)
  at Object.dispatch (node_modules/axios/index.cjs:?:?)
  at短路
  at AdjustedPassThrough.end (node_modules/axios/index.cjs:?:?)
]



feishu[default]: bot info probe timed out after 30000ms; continuing startup
feishu[default]: bot open_id resolved: unknown
feishu[default]: bot open_id unknown; starting background retry

### 网络对比

| 测试方式 | 结果 |
|---------|------|
| 浏览器访问 `open.feishu.cn` | ✅ 正常 |
| `curl https://open.feishu.cn` | ✅ 正常 |
| OpenClaw Gateway 访问 | ❌ 超时 |

### 问题首次发现时间
- 首次发现:`2026-04-01`
- 最近观察:`2026-04-06`
- 持续天数:5+
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Gateway 访问飞书 API(open.feishu.cn)反复超时(10s),但用户本地网络直连飞书服务器正常。

Steps to reproduce

NOT_ENOUGH_INFO

(无法从日志中确定触发条件,问题自发重复出现)

Expected behavior

Gateway 正常调用飞书 API,bot info probe 和 token 获取应在合理时间内完成。

Actual behavior

Gateway 访问飞书 API 反复超时,错误信息:

AxiosError: timeout of 10000ms exceeded
  • GET https://open.feishu.cn/open-apis/bot/v3/info — 10秒超时
  • POST https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal — 30秒超时
  • feishu: streaming start failed — 流式回复也超时

OpenClaw version

v2026.4.5(当前)、v2026.4.2、v2026.4.1(首次发现)、v2026.3.31(正常)

Operating system

Windows 11 23H2

Install method

npm install -g openclaw(全局安装)

Model

minimax-portal/MiniMax-M2.7

Provider / routing chain

Gateway (Windows) → feishu channel → open.feishu.cn API

Additional provider/model setup details

  • 使用飞书多个 bot(alpha_lead、alpha_backend、alpha_frontend、alpha_ui、alpha_qa、alpha_pm、alpha_reviewer、copywriter 等)
  • Gateway 通过飞书 WebSocket 长连接接收消息
  • 用户网络环境:中国大陆,访问 open.feishu.cn 正常(浏览器测试正常)
  • 问题仅出现在 OpenClaw Gateway 访问飞书 API 时

Logs, screenshots, and evidence

### 典型错误日志(已脱敏)


[error]: [
  AxiosError: timeout of 10000ms exceeded
  at onChartStreamTimeout (node_modules/axios/index.cjs:?:?)
  at Object.dispatch (node_modules/axios/index.cjs:?:?)
  at短路
  at AdjustedPassThrough.end (node_modules/axios/index.cjs:?:?)
]



feishu[default]: bot info probe timed out after 30000ms; continuing startup
feishu[default]: bot open_id resolved: unknown
feishu[default]: bot open_id unknown; starting background retry

### 网络对比

| 测试方式 | 结果 |
|---------|------|
| 浏览器访问 `open.feishu.cn` | ✅ 正常 |
| `curl https://open.feishu.cn` | ✅ 正常 |
| OpenClaw Gateway 访问 | ❌ 超时 |

### 问题首次发现时间
- 首次发现:`2026-04-01`
- 最近观察:`2026-04-06`
- 持续天数:5天+

Impact and severity

  • Affected users/systems/channels: 所有通过 Gateway 路由的飞书 bot(alpha_lead、alpha_backend、alpha_frontend、alpha_ui、alpha_qa、alpha_pm、alpha_reviewer、copywriter 等多个 agent)
  • Severity: blocks workflow — bot 启动时 open_id 获取失败,导致机器人身份无法恢复,消息处理延迟或失败
  • Frequency: always — 问题持续存在,重复出现
  • Consequence: 每次 Gateway 重启或 bot 重连时都需要等待后台 retry(60s、120s、300s、600s 递增延迟),影响消息响应速度和稳定性

Additional information

回归分析:

  • v2026.3.31:未观察到超时问题
  • v2026.4.1~v2026.4.5:开始出现超时问题
  • 推测可能是 v2026.4.x 某次更新改变了飞书 API 的 HTTP 客户端配置(如超时设置、连接池、DNS 解析、TLS 版本等)

用户本地网络验证:

  • 国内网络环境,访问飞书服务器本身无问题
  • 仅 OpenClaw Gateway 的 HTTP 请求超时
  • 可能是 Gateway 侧 HTTP client 的某些配置与中国网络环境不兼容

extent analysis

TL;DR

Adjust the HTTP client timeout settings in OpenClaw Gateway to improve compatibility with the Chinese network environment.

Guidance

  • Review the HTTP client configuration in OpenClaw Gateway, specifically the timeout settings, to ensure they are suitable for the Chinese network environment.
  • Compare the HTTP client settings between version v2026.3.31 and v2026.4.1 to identify any changes that may have introduced the timeout issue.
  • Consider increasing the timeout values for the GET and POST requests to open.feishu.cn to mitigate the timeout errors.
  • Verify that the DNS resolution and TLS version used by the HTTP client in OpenClaw Gateway are compatible with the Chinese network environment.

Example

No code snippet is provided as the issue is related to configuration and network compatibility.

Notes

The root cause of the issue is likely related to changes in the HTTP client configuration in OpenClaw Gateway, introduced in version v2026.4.1. The exact cause is uncertain, but adjusting the timeout settings and verifying DNS resolution and TLS version compatibility may help resolve the issue.

Recommendation

Apply a workaround by adjusting the HTTP client timeout settings in OpenClaw Gateway to improve compatibility with the Chinese network environment. This is recommended as the issue is likely related to configuration and network compatibility, and adjusting the timeout settings may help mitigate the timeout errors.

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

Gateway 正常调用飞书 API,bot info probe 和 token 获取应在合理时间内完成。

Still need to ship something?

×6

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

Back to top recommendations

TRENDING