Our problem is that the “createTranslationJob” method on the TranslationService Interface (com.adobe.granite.translation.api) is called twice for the same translation job project. The first time when the user clicks on “Request scope”. The second time when he clicks on “Start” after scoping is complete. Moreover, the translation objects are only uploaded to the first job and not the second one.
We would have expected that AEM calls “createTranslationJob” only once for a translation project and updates the status of the translation job from SCOPE_COMPLETE to COMMITED_FOR_TRANSLATION by calling “updateTranslationJobState”.
Why is “createTranslationJob” called twice?
Is there any way to figure out that createTranslationJob is called the second time for the same translation project? And what the returned job id of the first call is?