| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
You might sometimes experience an issue with your This article describes some possible reasons why translated content is not being delivered returned to the AEM CMS after you successfully finished a job /or project is finished in XTM Cloud. This article aims to present possible reasons behind such incidents as well as provide , and provides some troubleshooting guidelines.
...
Root cause of the issue
In the majority of cases, there are three potential reasons for failure in why target files reaching fail to return to the CMS:
Connection problems between the AEM CMS and XTM Cloud.
Failed target Target file generation fails on the XTM Cloud side.
Some other Other obscure problems occurring in your the AEM CMS at the momenttime.
...
Troubleshooting guidelines
Considering Troubleshooting should take all the root causes listed in the previous section , the troubleshooting process should look adequatelyinto account. See below.
Connection problems between the AEM CMS and XTM Cloud
You should make sure Ensure that the XTM Translation Cloud Configuration should be is properly configured for your site.
On your AEM CMS instance, access the following path:
/mnt/overlay/cq/translation/gui/content/cloudservices.html.Search for your XTM Cloud configuration and open it for editionediting.
Check that all the required data is provided and that no errors are displayed.
Go to
/services/xtm/rest-connection-test?configurationPath=<PATH_TO_XTM_CLOUD_CONFIGURATION>and check if the REST connection is working (i.e. http://localhost:4502/services/xtm/rest-connection-test?configurationPath=/conf/wknd/settings/cloudconfigs/translation/xtm/xtm).
| 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 to make sure that the relevant target file was has been generated successfully generated for a related XTM project in XTM Cloud. For this purpose, in XTM Cloud, enter a relevant the appropriate project, go to the Project Editor → Files section and check the status of your target file.
If you spot an actual error with the file generation error, it might be due to quite a few reasons. Read the following article, to try to identify the actual root cause as well as and find out how to resolve the problem: Target generation – most common issues & troubleshooting.
If, however, the target file was 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, there might be a suspicion that there is an issue on theside of the issue is likely to have occurred in your CMS.
In such cases, to assist you more effectively with the issues you are encountering with AEM, we always ask that you provide additional information whenever you report a problem.
Specifically, it would be extremely helpful if you could include the logs from the operation in question, in your JSM request. These logs are crucial for us to diagnose and resolve the issue promptly, as they provide detailed insights into what might be going wrong. Read the following article, to learn how to access and download logs from your CMS: AEM: Where are logs located and what information do they contain?.
| Note |
|---|
IMPORTANT! Note , that the logs may sometimes disappear over time, and replicating . Replicating the behavior again will generate new logs that the XTM Support team can analyze. Without these logs, it becomes challenging for them to investigate the problem thoroughly. |
Additionally, if possible, attach any relevant screenshots that illustrate the issue. This visual information can further aid the XTM Support team in understanding the problem context and specifics of the problem.