| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
This article describes some possible reasons why translated content is not returned to the AEM CMS after a job or project is finished in XTM Cloud, and provides some troubleshooting guidelines.
...
Root cause of the issue
In the majority of cases, there are three potential reasons why target files fail to return to the CMS:
Connection problems between the AEM CMS and XTM Cloud.
Target file generation fails on the XTM Cloud side.
Other obscure problems occurring in the AEM CMS at the time.
...
Troubleshooting guidelines
Troubleshooting should take all the root causes listed in the previous section into account. See below.
Connection problems between the AEM CMS and XTM Cloud
Ensure that the XTM Translation Cloud Configuration is properly configured for your site.
...
| Info |
|---|
If you would like to know more about managing a REST API connection, read the following article: AEM: How to check the REST API connection. |
Target file generation fails on the XTM Cloud side
The next step you should take is make sure that the relevant target file has been generated successfully for a related project in XTM Cloud. For this purpose, in XTM Cloud, enter the appropriate project, go to the Project Editor → Files section and check the status of your target file.
...
If, however, the target file has been generated correctly, the root cause might lie outside of the XTM Cloud environment.
Other obscure problems occurring in your AEM CMS at the time
Sometimes, the issue is likely to have occurred in your CMS.
...