I have configured Intento on the account, using the correct API key and custom routing name, both of which I can confirm work correctly on other systems. However, I am getting a “request to MT engine failed” for every segment. It’s not clear why this is. Any ideas?
1 Like
Hi there,
Please check Project tools → service logs, there should be a detailed response on why the action failed. Also, it’s worth checking user/API key permissions for MT. It should be manager/owner/admin (if it’s the Enterprise version).
Some tips to troubleshoot the issue from the side of the Intento:
- Verify your Intento subscription is active and supports the used MT engines.
- Test a simpler Intento routing (e.g., with a single provider like Google Translate) to isolate if the issue is within your custom route.
- Ensure language pairs are supported by all engines in your route.
- Check “Connected Accounts” within Intento if your route uses providers requiring separate authentication.
- Examine Intento Console API logs for specific error details.
Let me know if you found something interesting in the service logs or from the Intento side!
1 Like