langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 21:10:04 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Handling 429 error from Azure OpenAI #2220

New Issue
Closed
opened 2026-02-21 17:43:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:43:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @cnkang on GitHub (Apr 15, 2024).

Self Checks

  • 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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Yes, I am experiencing a challenge with the dify tool when using the Azure OpenAI Text Embedding 3 Large API. Specifically, I encountered a 429 error, which suggests that the tool is not handling rate limit responses (HTTP 429) from Azure OpenAI properly.

2. Describe the feature you'd like to see

I would like to see enhanced error handling in dify for HTTP 429 (Too Many Requests) responses from the Azure OpenAI API. Ideally, the tool should implement a retry mechanism that respects the Retry-After header provided by Azure. This feature should manage the request rate or pause the requests for the duration specified in the Retry-After header before retrying.

3. How will this feature improve your workflow or experience?

Implementing robust error handling for rate limit responses will significantly improve the reliability and usability of the tool when interacting with Azure OpenAI services. It will prevent the tool from stopping unexpectedly due to unhandled errors and ensure smoother, more consistent performance during high-frequency API interactions. This improvement will enable users like myself to maintain productivity without manually handling these interruptions.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @cnkang on GitHub (Apr 15, 2024). ### Self Checks - [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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Yes, I am experiencing a challenge with the dify tool when using the Azure OpenAI Text Embedding 3 Large API. Specifically, I encountered a 429 error, which suggests that the tool is not handling rate limit responses (HTTP 429) from Azure OpenAI properly. ### 2. Describe the feature you'd like to see I would like to see enhanced error handling in dify for HTTP 429 (Too Many Requests) responses from the Azure OpenAI API. Ideally, the tool should implement a retry mechanism that respects the Retry-After header provided by Azure. This feature should manage the request rate or pause the requests for the duration specified in the Retry-After header before retrying. ### 3. How will this feature improve your workflow or experience? Implementing robust error handling for rate limit responses will significantly improve the reliability and usability of the tool when interacting with Azure OpenAI services. It will prevent the tool from stopping unexpectedly due to unhandled errors and ensure smoother, more consistent performance during high-frequency API interactions. This improvement will enable users like myself to maintain productivity without manually handling these interruptions. ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:43:06 -05:00
yindo closed this issue 2026-02-21 17:43:06 -05:00
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 💪 enhancement
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#2220
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?