docs: 飞书 API 配额耗尽排查指南#48
Conversation
- Add troubleshooting entry in README for API quota being unexpectedly exhausted - Create docs/api-quota-fix.md with detailed diagnosis, root cause, and fix guide - Include copy-paste Agent prompt so users can fix it with any AI model
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fa4a2fa82f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| OpenClaw Gateway 内置了一个 **health check 定时器**，每 **60 秒**对所有已启用的 channel 执行一次健康探测（`probeAccount`）。 | ||
|
|
||
| 飞书插件的探测实现是调用 `GET /open-apis/bot/v3/info`——这是一个 REST API 调用，**每次都计入飞书月度配额**。 |
There was a problem hiding this comment.
This guide says the health check consumes quota by calling GET /open-apis/bot/v3/info, but the actual probe implementation in this repo calls POST /open-apis/auth/v3/tenant_access_token/internal (src/probe.ts, probeFeishu). Because the copied remediation prompt repeats the bot/v3/info claim, users troubleshooting via API logs will look at the wrong endpoint and can misdiagnose whether the change worked.
Useful? React with 👍 / 👎.
1 participant
背景
在几乎没有使用飞书机器人的情况下，发现飞书 API 月度配额（50,000 次）被耗尽。排查发现是 OpenClaw Gateway 的 health check 机制导致：每 60 秒调用一次
bot/v3/infoAPI，计入飞书配额。改动
README.md
docs/api-quota-fix.md（新增）