openclaw - 💡(How to fix) Fix Windows Gateway Feishu API timeout 30s at startup [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#63257Fetched 2026-04-09 07:56:11
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Error Message

AxiosError: timeout of 30000ms exceeded url: 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal'

RAW_BUFFERClick to expand / collapse

Bug: Windows Gateway Feishu API timeout 30s at startup

Problem Description

On Windows, Gateway startup causes Feishu API (open.feishu.cn) to timeout after 30 seconds, but system network is normal.

Environment

  • OS: Windows 11
  • Node.js: v24.14.1
  • OpenClaw Version: 2026.4.8
  • Feishu SDK: @larksuiteoapi/node-sdk (axios)

Reproduction Steps

  1. Start Gateway (openclaw gateway start)
  2. Observe logs showing eishu API timeout
  3. After 30 seconds, Gateway continues startup and Feishu works normally

Logs

AxiosError: timeout of 30000ms exceeded url: 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal'

Test Results

Test MethodLatencyResult
PowerShell Invoke-WebRequest0.5sSuccess
Node.js axios (Gateway)30s timeoutFail

Expected Behavior

Gateway should connect to Feishu API quickly at startup without 30s timeout.

Additional Info

  • Network DNS is normal (tested)
  • No proxy
  • Feishu WebSocket connects successfully after startup (features work fine)

extent analysis

TL;DR

  • Adjusting the timeout setting in the Feishu SDK or Axios configuration may resolve the 30-second timeout issue at Gateway startup.

Guidance

  • Review the Axios configuration in the Gateway to ensure the timeout is not set too low, considering the Feishu API's response time.
  • Compare the DNS resolution and network connectivity between PowerShell and Node.js environments to identify any discrepancies.
  • Verify if there are any specific requirements or recommendations from Feishu for handling timeouts or connection establishment.
  • Consider implementing a retry mechanism with exponential backoff for handling temporary connection issues.

Example

// Example of adjusting timeout in Axios
const axios = require('axios');
axios.defaults.timeout = 60000; // Set timeout to 1 minute

Notes

  • The issue seems specific to the Node.js environment, as PowerShell tests do not exhibit the same timeout behavior.
  • It's unclear if the Feishu API has specific requirements for handling timeouts or if there are known issues with the @larksuiteoapi/node-sdk version being used.

Recommendation

  • Apply workaround: Adjust the timeout setting and consider implementing a retry mechanism to handle temporary connection issues, as the root cause of the discrepancy between PowerShell and Node.js environments is not immediately clear.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING