Pascal Linxweiler e70b432fe6 Explain the DeepL glossary limit instead of forwarding the raw error ...

Saving terms for a domain/direction that has no glossary yet skips the
delete-before-create step, so the create runs against an account whose
glossary allowance may already be spent. DeepL answers 456 with a bare
{"message":"Too many glossaries"}, which was passed straight to the browser
and reads like a bug in this app.

On the API Free plan the allowance is one glossary for the entire account,
so this triggers as soon as a second domain or direction is used — the UI
offers eight slots (4 domains x 2 directions) that the plan cannot back.

The 456 case now reports which glossaries hold the slots and names the two
ways out: free one up, or upgrade the plan.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-07-31 11:54:26 +02:00

22 KiB

Raw Blame History

View Raw