Skip to content

Conversation

rafaelmardojai
Copy link
Member

This is needed by the DeepL provider, and they recommend it in their API docs, since the service is expected to return "HTTP 429: too many requests" errors when sending many API requests in a short period of time.

https://developers.deepl.com/docs/best-practices/error-handling

Fixes #433

@rafaelmardojai rafaelmardojai requested a review from mufeedali May 20, 2025 16:32
This is needed by the DeepL provider, and they recommend it in their
API docs, since the service is expected to return "HTTP 429: too many
requests" errors when sending many API requests in a short period of
time.
@mufeedali mufeedali merged commit b6795f0 into main May 26, 2025
2 checks passed
@mufeedali mufeedali deleted the fix-deepl branch May 26, 2025 20:16
@mufeedali
Copy link
Member

LGTM. I'm still unable to reproduce the issue from my end though... Very odd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DeepL provider fails on startup

2 participants