Error 429 (Rate Limit)

DeepL limits the number of requests per time unit. When exceeded, the API responds with HTTP 429 (“Too Many Requests”) and a Retry-After header indicating the recommended wait time.

Plugin Behaviour

• Automatic retry: up to 3 further attempts per text
• The wait time communicated by DeepL (Retry-After header) is honored; without a header, 5 seconds are used
• Afterwards the job fails and the error message (including “429”) appears in the queue view

What to Do About Frequent 429 Errors?

1. Check quota: under Content > Translation with DeepL > DeepL Usage you can see the consumption. With an exhausted quota retries do not help, see FAQ: Free vs. Pro.
2. Reduce job size: spread large runs across time windows (e.g. products first, then categories) or use filters/whitelists.
3. Use the cache: without “Ignore cache”, recurring texts consume no quota, see FAQ: Cache.
4. Throttle workers: Shopware allows limiting worker concurrency via the message queue configuration, see Shopware docs: message queue.
5. Run again: failed jobs can be re-queued individually or in bulk via the queue view; already cached texts then run through quickly.