Hi Brigitte Martin , We are unable to reproduce the scenario. When we tried, it successfully filled target segments. 

Please provide more details (step by step) to reproduce the scenario so that we can help you further. 

Thanks!

Patrick Andrew Hartnett 

Hi Harjeet, thank you for your response. When creating the project online there are no issue using the same template, it happens only when using the API. 

1. From the project creation window, we type in the name the project
2. Then we choose the appropriate template (list of templates matches those in Trados Team)
3. Then click OK to create the project
4. The various steps of project creation in Trados Team appear, including Machine Translation as per the selected Project template

5. And then when checking in Trados Team, NMT is not applied

Hi Harjeet, 

Please find below more details on the steps. I hope this helps. We really need to resolve this issue quickly.

• Create Project
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: POST https://api.eu.cloud.trados.com/public-api/v1/projects
  Request Body:

{
  "name":"2176248",
  "location":"d483666e380e412db6edea1f82c90d4f",
  "dueBy":"2025-06-10T12:30:02.213Z",
  "projectTemplate":
  {
    "id":"6749d65cacd10538233da6ec"
  },
  "languageDirections":
  [
    {
      "sourceLanguage":
      {
        "languageCode":"EN-GB"
      },
      "targetLanguage":
      {
        "languageCode":"FR-FR"
      }
    }
  ],
  "projectManagers":
  [
    {
      "id":"65008d0c845e401182eff831",
      "type":"user"
    }
  ]
}

Response: 201

{
 "id":"6848254b5c257855dcaa75f0",
 "name":"2176248",
 "languageDirections":
 [
  {
   "sourceLanguage":
   {
    "languageCode":"en-GB",
    "englishName":"English (United Kingdom)"
   },
   "targetLanguage":
   {
    "languageCode":"fr-FR",
    "englishName":"French (France)"
   },
   "id":"6848254a5c257855dcaa75ee"
  }
 ],
 "location":
 {
  "id":"d483666e380e412db6edea1f82c90d4f",
  "name":"xxxxxx"
 }
}

• Add File
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: POST https://api.eu.cloud.trados.com/public-api/v1/projects/6848254b5c257855dcaa75f0/source-files
  Request Body:

{
 "name":"document2.docx",
 "role":"translatable",
 "type":"native",
 "language":"EN-GB",
 "targetLanguages":
 [
  "FR-FR"
 ]
}

Response: 201

{
 "id":"684825da75e6065ca90596f5",
 "name":"document2.docx",
 "role":"translatable"
}

• Start project
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: PUT https://api.eu.cloud.trados.com/public-api/v1/projects/6848254b5c257855dcaa75f0/start
  Response: 202

Hi Harjeet, 

Please find below more details on the steps. I hope this helps. We really need to resolve this issue quickly.

• Create Project
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: POST https://api.eu.cloud.trados.com/public-api/v1/projects
  Request Body:

{
  "name":"2176248",
  "location":"d483666e380e412db6edea1f82c90d4f",
  "dueBy":"2025-06-10T12:30:02.213Z",
  "projectTemplate":
  {
    "id":"6749d65cacd10538233da6ec"
  },
  "languageDirections":
  [
    {
      "sourceLanguage":
      {
        "languageCode":"EN-GB"
      },
      "targetLanguage":
      {
        "languageCode":"FR-FR"
      }
    }
  ],
  "projectManagers":
  [
    {
      "id":"65008d0c845e401182eff831",
      "type":"user"
    }
  ]
}

Response: 201

{
 "id":"6848254b5c257855dcaa75f0",
 "name":"2176248",
 "languageDirections":
 [
  {
   "sourceLanguage":
   {
    "languageCode":"en-GB",
    "englishName":"English (United Kingdom)"
   },
   "targetLanguage":
   {
    "languageCode":"fr-FR",
    "englishName":"French (France)"
   },
   "id":"6848254a5c257855dcaa75ee"
  }
 ],
 "location":
 {
  "id":"d483666e380e412db6edea1f82c90d4f",
  "name":"xxxxxx"
 }
}

• Add File
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: POST https://api.eu.cloud.trados.com/public-api/v1/projects/6848254b5c257855dcaa75f0/source-files
  Request Body:

{
 "name":"document2.docx",
 "role":"translatable",
 "type":"native",
 "language":"EN-GB",
 "targetLanguages":
 [
  "FR-FR"
 ]
}

Response: 201

{
 "id":"684825da75e6065ca90596f5",
 "name":"document2.docx",
 "role":"translatable"
}

• Start project
  X-LC-TraceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  Request URL: PUT https://api.eu.cloud.trados.com/public-api/v1/projects/6848254b5c257855dcaa75f0/start
  Response: 202

Hi Brigitte Martin ,

Thanks for sharing additional information! We are able to reproduce the issue now. 

We have started working on the fix and will update you shortly on the same. 

Hi Harjeet,

Great thank you, looking forward!

Hello  , can you please give me an update ? When will the issue be resolved? Please let me know. Best, Brigitte

Hi Brigitte Martin ,

We have published new DeepL MT App version [v1.6.13] in PROD today. Would you please update the same on your tenant and check if it fixed the issue?

Thanks!

Hi  ,

Great news thank you ! I will test and get back to you.

Best,

Brigitte

Hello again Harjeet, 

I have tested and I confirm that the target segments are filled in with NMT.

Thank you so much for your help!

Best,

Brigitte 

Hello Harjeet,

Another issue came up while testing. The wordcount is in the report in MT category. Was it not in the New/AT category before?

We now end up with 0 new words to translate when using the API.

Get you please explain the difference and wy NEw/AT is empty now?

Thank you in advance

Best,

Brigitte

Brigitte Martin 

Worth noting that AT is "Automated Translation" and not MT or NMT.  In the old days AT was MT, but now we differentiate between the two.  "Automated Translation" relates to anything Trados Studio handles automatically (such as numbers for example) without any machine translation engine attached at all, and it only kicks in when the target is empty... hence the reason it falls in with "New".

Hi Paul, thank you for your response. What do you mean with old days ? Can you specify in which version the change occured (Trados 2024 or even before ?)

Best,

Brigitte

 Brigitte Martin 

I mean, with older versions.  It is related to the massive improvements we have seen with NMT and how workflows have adapted as a result.  So at some point we switched to have all machine translation providers use NMT (as nobody uses statistical any more) and give the results that status.  This also allowed us to remove the confusion over where AT results came from since they are often generated from the TM itself and not machine translation at all.

Using NMT as opposed to AT was definitely prior to 2024.  With regard to the analysis change I can only find reference to 10 December 2024 (CU13 release) onward, where GroupShare began reporting NMT in its own category rather than under AT/New.  The changes in Trados Studio were more under the hood and made over a number of releases starting towards the end of 2021.