Some error messages will appear whenever we are missing some settings for the translation request to properly reach our pipeline, or if those settings are not consistent with your customer profile at Unbabel. Below, we are describing those messages and listing the steps to take in order to solve any issues.
Whenever you need to reach out to support or the suggested steps are not working, find us at firstname.lastname@example.org, and we will be glad to help you out.
- Invalid subscription
If this message appears, either the language is not added to Customer Language field in the Unbabel Widget (most likely to avoid an outbound translation request in the unsupported language), or the source language is not subscribed even though the request is made in that language. Check if the language is actually subscribed and if it is, reach out to support.
- No target language provided
An internal note containing #unbabel is being posted but no language is selected. Select a subscribed language and try again.
- Unbabel not active
The note containing #unbabel was posted while the activation value was empty or set to False. Activate it and try again - check the detected customer language first!