Documentation Center

Troubleshooting Error Retrieving

When errors occur retrieving Translation Jobs, you can try a number of troubleshooting steps to solve the problem.

Item does not exist
Problem: The item that was included in a Translation Job has since been deleted in the Content Manager.
Solution: You can ignore the problem as items are retrieved one-by-one, so successfully translated and retrieved content is unaffected by the problem.
Item not valid according to its Schema
Problem: The Schema of an item has changed since it was translated, rendering the item invalid.
Solutions: Do one of the following, then click Retry Retrieving.
  • Roll back the Schema changes temporarily
  • Ignore the error, update the item to make it valid, and resend it in a new Translation Job
Network connection
Problem: Content Manager cannot connect to the translation system.
Solution: Check your remote translation system is running by logging on to it directly. If it is up, wait a few minutes before Retry Retrieving; if it is down, contact your system administrator.
Unexpected SDL WorldServer behavior
The following problems may explain certain irregular behavior relating to SDL WorldServer:
  • Workflow status:
    • Delays in reflecting Workflow status—it can take up to a day or more to reflect changes in the Workflow status of translations in Content Manager
    • Subworkflows are not relected in Content Manager
  • Translation Job set to Canceled—Content Manager considers any item that reaches Finish stage without being picked up by Translated Content Retrieval as Canceled. You must therefore make sure to create a Translated Content Retrieval step as a human step as it needs to be 'manually' moved on (the step is not supposed to be handled by any human user—it is recommended to assign a dummy user to this step).