azure openai rate limit error code 429 #7706

Closed
opened 2026-02-21 18:21:58 -05:00 by yindo · 2 comments
Owner

Originally created by @daizhiqi on GitHub (Jan 13, 2025).

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.13.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Upload several large documents and use the file extractor to extractor. Then transfer the extracted information into 10 LLMs at the same time to separately produce different information. Usually the error will happen in only one of the LLMs while others had already turned out results.
截屏2025-01-14 11 14 42
截屏2025-01-14 11 14 59
Already checked the largest token set on azure is 450k, so it had not exceeded. Do not know why it happened and any ways to solve it? It had happened several times.

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @daizhiqi on GitHub (Jan 13, 2025). ### 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.13.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Upload several large documents and use the file extractor to extractor. Then transfer the extracted information into 10 LLMs at the same time to separately produce different information. Usually the error will happen in only one of the LLMs while others had already turned out results. <img width="596" alt="截屏2025-01-14 11 14 42" src="https://github.com/user-attachments/assets/947be472-793f-4081-aaa9-1ae930586cfd" /> <img width="558" alt="截屏2025-01-14 11 14 59" src="https://github.com/user-attachments/assets/2cad2ca5-7dd3-4404-a649-6d9524969eb0" /> Already checked the largest token set on azure is 450k, so it had not exceeded. Do not know why it happened and any ways to solve it? It had happened several times. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:21:58 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jan 13, 2025):

@daizhiqi Hello there! 👋 I'm here to help you with bugs, questions, and more while you wait for a human maintainer.

I found some similar discussions regarding Azure OpenAI rate limit errors:

  1. Help: Request error: Run failed: [openai] Rate Limit Error, Error code: 429 - This discussion is unsolved and mentions a similar rate limit issue with OpenAI's API [1].

  2. Handling 429 error from Azure OpenAI - Another unsolved discussion that addresses handling 429 errors from Azure OpenAI [2].

To address the rate limit error you're encountering, consider implementing retry logic with exponential backoff. This approach is recommended for handling rate limit errors in Dify [3]. Additionally, you might want to check the OpenAI documentation for details on rate limits and consider adding a payment method to your account to potentially increase your rate limit [4].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Jan 13, 2025): <!-- Greeting --> @daizhiqi Hello there! 👋 I'm here to help you with bugs, questions, and more while you wait for a human maintainer. <!-- Answer --> I found some similar discussions regarding Azure OpenAI rate limit errors: 1. [Help: Request error: Run failed: [openai] Rate Limit Error, Error code: 429](https://github.com/langgenius/dify/discussions/11806) - This discussion is unsolved and mentions a similar rate limit issue with OpenAI's API <sup>[[1]](https://github.com/langgenius/dify/discussions/11806)</sup>. 2. [Handling 429 error from Azure OpenAI](https://github.com/langgenius/dify/discussions/3493) - Another unsolved discussion that addresses handling 429 errors from Azure OpenAI <sup>[[2]](https://github.com/langgenius/dify/discussions/3493)</sup>. To address the rate limit error you're encountering, consider implementing retry logic with exponential backoff. This approach is recommended for handling rate limit errors in Dify <sup>[[3]](https://github.com/langgenius/dify/issues/11694)</sup>. Additionally, you might want to check the OpenAI documentation for details on rate limits and consider adding a payment method to your account to potentially increase your rate limit <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/use-llms-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/7800bf64-6d02-412b-b981-d77b8987ce57?feedback_type=other)</sup>
Author
Owner

@crazywoola commented on GitHub (Jan 13, 2025):

We can not fix rate limit issue for you, I suggest you increase pay tier or contact them instead.

@crazywoola commented on GitHub (Jan 13, 2025): We can not fix rate limit issue for you, I suggest you increase pay tier or contact them instead.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7706