Salesforce

SDL Worldserver - Error at 'Generate Translation Kit' Workflow Step or 'Create Project Package' - 'Only human steps can be claimed! '

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer
Symptoms/Context
A Task fails at Generate Translation Kit or (starting from WorldServer 11.6.) at Create Project Package step with following error

Only human steps can be claimed!

The complete error includes generic information about the Generate Translation Kit step and is not really helpful. Here is the remaining error text:

Task step: com.idiominc.ws.workflow.engine.TaskStep [ id = 16720433, name = Generate Translation Kit, description = Automatic step executing automatic action Generate Translation Kit. Generates a translation kit in the specified format (WSXZ, XLZ, TRADOS TTX, XLIFF, or Bilingual DOCX) and writes it out to a user-specified location which is set in the 'Output Directory' parameter. The file generated will be named with the format: project_< project_name >_< ID >_< locale >_.< wsxz | xlz | zip >. The third parameter is optional but, when set, will store the generated translation kit in the specified project file attachment attribute. This can be useful if there are other steps in the workflow that can use the generated translation kit, task id = 716100, task display id = 1... Affected project (Number – Project Name – Language) ....

or

Completed Create Project Package step of task 1 in time [00:00:00] on engine [xxx114x:clone#1491908397:engine#8] with result Error. Execution output: Only human steps can be claimed! Task step: com.idiominc.ws.workflow.engine.TaskStep [ id = 199418, name = Create Project Package, description = Automatic step executing automatic action Create Project Package. Generates a translation kit in the specified format (WSXZ, XLZ, XLIFF, or Bilingual DOCX) and writes it out to a user-specified location which is set in the ''Output Directory'' parameter. The automatic action must be followed by a human step assigned either to the user corresponding to the TranslationKitUser parameter in the project''s attributes or, by default, to the project''s creator. 
Resolution
The resolution is to add a human step, for instance Translate after Generate Translation Kit (or Create Project Package). Since the WSXZStudio package is exported for users to be downloaded and opened in SDL Trados Studio, it is recommended that the human step is added right after Generate Translation Kit (or Create Project Package). Here is an example of a simple workflow with Generate Translation Kit followed by human step:

User-added image


If you use Create Project package, you *must* use Tasks as Kit Exporter Type so you have to configure your workflow to add a human step after Create Project package. The workaround below will not work.

If you use Generate Translation Kit, the workaround is to configure the Generate Translation Kit in the Workflow to use the Kit Exporter Type: Assets instead of Tasks as displayed here: 

User-added image

Save the change in the Workflow and re-submit the project. The project with the tasks in Autoerror will need to be canceled. 

Warning: if you select Kit Exporter TypeAssets, the exported WSXZ package will be named after the project, for instance: project_Test Generate Translation Kit_1_1529_Dutch (Netherlands)_workbench.wsxz. However, once you open the package in SDL Trados Studio, it will display with a  generic project name isuch as Adhoc_Project_xxxxxxx_xxxxxx"(where the first 8 digits stand for the date of the export and the last 6 digits are random). This might be confusing as the translator will not be able to see the actual project name in Studio. Here is an example:

User-added image

More information about how to configure the Generate Translation Kit workflow step can be found in this article:

SDL WorldServer - How to configure the Generate Translation Kit Automatic Action and add it to your Workflow

 
Root Cause
The Generate Translation Kit and the Create Project Package step has been configured to use the Kit Exporter Type: Tasks. If you use Tasks, the next step after Generate Translation Kit must be a human step, for instance Translate
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by