Timo Brembeck

I mean, in theory we can also outsource the storing of information to DeepL itself. And only query the stored entries from time to time and store them in our...

Ah ok, just read the API docs, and apparently glossaries can only be created and deleted, not modified. So modification only works via retrieving, then modifying locally, then deleting the...

Wait, we already have a DeepL Pro Advanced account? Then the basic functionality we're talking about here should already be offered by the DeepL web UI (see [here](https://support.deepl.com/hc/en-us/articles/360021638100-Glossary-availability))? I think...

Indeed: 

Oh, and I noticed another problem: we use two differrent accounts: the glossary can only be uploaded via the UI for the "DeepL Pro" account and we perform our automated...

> Do you need any more input from our side on this? Probably yes: So as far as I understood it, we sadly cannot use the DeepL Pro account glossary...

> I am not sure if this is feasible though due to case declination of words (Dativ, Genitiv, etc Anpassung...) Hmm, in my opinion we're opening Pandora's Box here :sweat_smile:...

@osmers good catch! > Question remains whether we can use it - would it help if we switched to the DeepL Pro Account to use the API and Glossary? Or...

A similar issue occured on March 14 when acquiring the db mutex: Traceback ``` Mar 14 12:43:53 ERROR django.request - 500 Internal Server Error: /landkreis-konstanz/pages/de/14907/edit/ Traceback (most recent call last):...

@svenseeberg yes, I agree. Very strange... But this relates mostly to issue #1518, right?