---
description: >-
  This page lists some reasons you may have issues submitting or receiving
  Translation Jobs.
---

# Appendix 2: Troubleshooting

## If you are **Unable to submit Translation jobs:**

Error: “**Error Sending Job**”

&#x20;If you receive this error while make a submission, then the Translation Job will not send. Below are possible reasons that your Translation Job receives this error when attempting to make a submission:&#x20;

**There is no translatable content to be sent for the target languages selected. Check that the job contains fields that require translation.**



### Scenario 1: Last Modified dates

* The connector uses timestamps / last modified dates of Fields to determine what content requires translation when the Entity is included in a Translation Job.
* If the last modified date of the source field is later than the target field then it will not be sent for translation for that language.
*
  * These fields will still be included in the exported xml file, and marked as translate=”false”.
* If all fields in an entity have last modified date of the source field is later than the target field then the entity will not be included in the exported xml file at all.
* If all entities have all fields where last modified date of the source field is later than the target field then nothing can be sent for translation so the Translation job will fail with error “**Error Sending Job**”



### &#x20;Scenario 2: Content In Translation

* The connector maintains the translation status of the entities that it send for translation. If an entity has been included in a Translation Job that is still In Translation (ie not Imported yet) then any fields that are currently “out for translation” will be assessed by the connector as not requiring translation (unless the source is modified)
*
  * These fields will be marked as translate=”false”
* If all fields in an entity are currently In Translation then the entity will not be included in the exported xml file at all.
* If all entities have all fields currently In Translation then nothing can be sent for translation so the Translation job will fail with error “**Error Sending Job**”

### &#x20;**The content that you're submitting contains “illegal” characters.**&#x20;

#### **Please check and remove “illegal” characters.**

* If the content of any entities that you are submitting contains an “illegal” character, then the Translation job will fail with error “**Error Sending Job**”
* This is a validation step by inRiver that checks for these characters not a connector validation.
* A list of the characters that fail inRiver validation is listed below and will need to be removed from content before submission will be made.

(Note 1:The connector is not able to retrieve the identity of the entity that contains the “illegal” character from inRiver.

(Note 2: As this is an inRiver validation, the list is subject to changes made by inRiver)

&#x20;

\[ASCII: 0] \[NULL]

\[ASCII: 1] \[Start of Heading]

\[ASCII: 2] \[Start of Text]

\[ASCII: 3] \[End of Text]

\[ASCII: 4] \[End of Transmission]

\[ASCII: 5] \[Enquiry]

\[ASCII: 6] \[Acknowledge]

\[ASCII: 7] \[Bell]

\[ASCII: 8] \[Backspace]

\[ASCII: 9] \[Horizontal Tabulation]

\[ASCII: 11] \[Vertical Tabulation]

\[ASCII: 12] \[Form Feed]

\[ASCII: 14] \[Shift Out]

\[ASCII: 15] \[Shift In]

\[ASCII: 16] \[Data Link Escape]

\[ASCII: 17] \[Device Control One]

\[ASCII: 18] \[Device Control Two]

\[ASCII: 19] \[Device Control Three]

\[ASCII: 20] \[Device Control Four]

\[ASCII: 21] \[Negative Acknowledge]

\[ASCII: 22] \[Synchronous Idle]

\[ASCII: 23] \[End of Transmission Block]

\[ASCII: 24] \[Cancel]

\[ASCII: 25] \[End of Medium]

\[ASCII: 26] \[Substitute]

\[ASCII: 27] \[Escape]

\[ASCII: 28] \[File Separator]

\[ASCII: 29] \[Group Separator]

\[ASCII: 30] \[Record Separator]

\[ASCII: 31] \[Unit Separator]



## If you are **Unable to Import Translation Jobs:**

&#x20;**Translation Job does not show “Ready to download”.**

You have submitted your Translation Job, but are unable to Import it after Lionbridge has delivered it back. Below are possible reasons that your Translation Job Is not able to be Imported.

&#x20;

* If the Lionbridge Extensions in the Control Center have been disabled then the connector will not be able to receive the delivery until they are re-enabled.
* If the inRiver language codes have changed after the Translation Job was submitted then the connector cannot process the delivered files as the codes no longer match.
* If the Freeway delivered file was not formatted correctly, then the connector will not be able to receive the delivery.
*
  * To verify if this is the case please contact your Lionbridge PM directly or the Connector Support team alias [connectors@lionbridge.com](mailto:connectors@lionbridge.com)
