Logfiles and Debugging
Check the Message Queue
Section titled “Check the Message Queue”Translation jobs run asynchronously via the Shopware message queue. The status of each job (pending, running, completed, failed) is visible under Content > Translation with DeepL > Queue, including the error message of failed jobs.
A running worker is required for processing:
bin/console messenger:consume asyncShopware Log
Section titled “Shopware Log”Warnings and errors of the translation services are written to the standard Shopware log:
tail -f var/log/dev.log | grep "SATAG"In production environments the log is located under var/log/prod-*.log or according to your logging configuration.
CLI Commands
Section titled “CLI Commands”Translate a snippet set
Section titled “Translate a snippet set”php bin/console satag:snippets:translate <source-snippet-set-id> <target-snippet-set-id>Options:
| Option | Description |
|---|---|
--glossary <id> / -g <id> |
Use a DeepL glossary for this translation |
--ignore-cache |
Ignore the cache and force re-translation |
The command queues the jobs; the translation is processed asynchronously by the worker.
Behaviour on DeepL Errors
Section titled “Behaviour on DeepL Errors”| Situation | Behaviour |
|---|---|
| HTTP 429 (rate limit) | Automatic retry, up to 3 attempts; the wait time delivered by DeepL (Retry-After header) is honored. Afterwards the job fails and shows the error message in the queue. Details: FAQ: Error 429 |
| Network errors | Job fails with a connection error in the error message; retry via the queue view possible |
| Wrong glossary (e.g. language pair mismatch) | Job fails, the DeepL error message is visible in the queue |
| Quota exhausted | DeepL error message visible in the queue; check quota under Content > Translation with DeepL > DeepL Usage |