Translation jobs stuck and not processed

[mayank-saxena1987]

We have AEM system integrated with ETMA  support. We have added pages in translation jobs with Human Translation method and From Master English(US) to multiple languages.
After submission status remains to Submitted for some jobs and Committed for translation for other jobs.

It should be Translation in progress as per the flow.

ETMA translation vendor team confirmed that they haven't received any jobs in their system.
We are unable to get anything what went wrong  into backend as everything we did was right. This situation arises many times and jobs get stuck in backend.

We don't have Felix console access due to security measures. What should we need to ask support team to get the root cause of this or what could be the issue of this.

What is the possible cause of these jobs get stuck into the system and not processed for translations.

Please help as this occurred many times and we need to recreate jobs one by one deleting lang masters.

Also suggest, Is it possible to display any notification or message during/before Starting Translation Job to display if any service cause the issue to process the job smoothly and revert to DRAFT state without submission?

Is it possible to save our time, we can revert the same corrupted jobs to DRAFT status from backend to resend the same for translation without recreating the new jobs and adding the pages?

@kautuk_sahni @aanchalsikka 

[aanchal-sikka · Accepted solution]

Hello @mayank-saxena1987 

Please check the AEM's logs for any errors.

• With translation the issues often arise due to concurrency. Please check for any OakState0001 exception. Details about this error are on: https://helpx.adobe.com/in/experience-manager/kb/how-to-find-conflicts-when-getting-oakstate0001.htm...
• Check for any failures while connecting to the vendor for translation.

If the logs are not detailed enough, please try switching the log levels temporarily and capture more details.

Resetting the translation jobs status to DRAFT should be the last resort.