When a translation job is submitted to gengo might happen that not all data items get its gengo job but are put to status "held" and no data returned.

The problem is that we either receive jobs upon translation requests, so we go for mappings creation or we dont and that time we just create a placeholder for future mappings. This case that just occured is something in between - so we have gengo jobs but not for all we are able to create mapping.

We need to identify such case and create mappings for jobs we have and in addition to that also create the placeholder

Comments

issam.zeibak’s picture

issam.zeibak commented

Apologies for my late reply. I replied to MD Systems offline regarding this issue but need to clarify some more.

There are two instances where you will get the status "held":

1. On our live system, in the case that there is a technical problem with a job. In this case a support agent with admin access will "hold" the job until any and all issues with it are resolved. Our suggestion is that this can be treated in the system as "pending", since the job is being worked on and will be resolved soon.

2. This was a bug we had in our sandbox in April. Once the delete button was pressed for deleting the old jobs, some records were in a limbo stage where they showed they were being "held'. THis happened for old data that was 100% matching. We are still working on fixing this bug for old data, however any newly created data will be fine. Modifying the data sent during tests, even by a character, should work for now until all old data is updated.

We are also currently working on making our development docs clearer to list this held status along with any other statuses.