Describe the bug
We noticed that if a glossary is existing, which contains entries, but is out-of-sync with DeepL (the Glossary ID can't be found with DeepL API), translations are not working. The translation will then only contain the original language.
To Reproduce
unsure
Expected behavior
Check against API if Glossary ID is know by DeepL API, otherwise show an error message (eg. as flash message in TYPO3 backend)
Workaround
Manually sync the glossary from the TYPO3 backend.