langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-25 13:36:01 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

ZhiPu APIReachLimitError #5538

New Issue
Closed
opened 2026-02-21 18:11:30 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:11:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @koalababy2024 on GitHub (Sep 11, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.8.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

企业微信20240911-134333

Today, I registered a new zhipu ai key.
As screenshot shows, it shows APIReachLimitError.
When I changed the new key with the old key which I registered several days before. It works.

✔️ Expected Behavior

the new zhipu key works.

❌ Actual Behavior

the new zhipu key not works.

Originally created by @koalababy2024 on GitHub (Sep 11, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.8.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![企业微信20240911-134333](https://github.com/user-attachments/assets/8e8b6870-b4ee-4c1d-aa94-01028ac42d47) Today, I registered a new zhipu ai key. As screenshot shows, it shows APIReachLimitError. When I changed the new key with the old key which I registered several days before. It works. ### ✔️ Expected Behavior the new zhipu key works. ### ❌ Actual Behavior the new zhipu key not works.
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:11:30 -05:00
yindo closed this issue 2026-02-21 18:11:30 -05:00
yindo commented 2026-02-21 18:11:30 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 11, 2024):

If you encounter a rate-limit error, please upgrade your billing or contact their support to upgrade the limit. We can do nothing but report an error.

@crazywoola commented on GitHub (Sep 11, 2024): If you encounter a rate-limit error, please upgrade your billing or contact their support to upgrade the limit. We can do nothing but report an error.
yindo commented 2026-02-21 18:11:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 11, 2024):

The APIReachLimitError with the new ZhiPu AI key likely indicates that the new key has reached its API call rate limit. This can happen if the new key has exhausted its allowed number of API calls within a given time frame, whereas the old key has not yet reached its limit [1][2].

For more details, you might want to check the specific rate limits and quotas for API calls using ZhiPu AI keys as documented in the Dify platform. If you need to adjust the concurrency or rate limits for ZhiPu AI API calls, you may need to look into the configuration settings in Dify, although specific details on this were not found in the repository [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 11, 2024): <!-- Answer --> The `APIReachLimitError` with the new ZhiPu AI key likely indicates that the new key has reached its API call rate limit. This can happen if the new key has exhausted its allowed number of API calls within a given time frame, whereas the old key has not yet reached its limit <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/use-llms-faq.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/learn-more/faq/llms-use-faq.md)</sup>. For more details, you might want to check the specific rate limits and quotas for API calls using ZhiPu AI keys as documented in the Dify platform. If you need to adjust the concurrency or rate limits for ZhiPu AI API calls, you may need to look into the configuration settings in Dify, although specific details on this were not found in the repository <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/use-llms-faq.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/learn-more/faq/llms-use-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug 🤔 cant-reproduce
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5538
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?