“Source File Not Linked to Task” When Adding New File Version

  

We are currently working on an integration using the Trados Cloud Public API and have encountered difficulties while attempting to add a new version to an existing source file using the corresponding endpoint (Trados Cloud Platform API Documentation).

Summary of Attempts

We have thoroughly reviewed the documentation and tested the endpoint in multiple scenarios. Some API responses were clear and helped us correct our requests. For instance:

{

    "errorCode": "taskCompleted",

    "message": "Adding source file version is not allowed when the task is completed."

}

White check mark We ensured that the task is in an active state before retrying the request.

 

{

    "errorCode": "noOwner",

    "message": "The task has no owner."

}

{

    "errorCode": "differentOwner",

    "message": "The task has a different owner."

}

White check mark We verified and corrected the task ownership to match the user making the request.

 Despite these corrections, we are now facing errors that we haven't been able to resolve. The most frequent blocking issue is the following:

{

    "errorCode": "invalid",

    "message": "The provided source file is not linked to given task.",

    "details": [

        {

            "name": "sourceFileId",

            "code": "invalid",

            "value": "67f5403c875f471d981cf706"

        }

    ]

}

We confirmed that the sourceFileId we are sending belongs to the project associated with the task. However, the API still rejects it.

As a test, we also tried using a target file ID, which resulted in:

{

    "errorCode": "notFound",

    "message": "Source file could not be found.",

    "details": [

        {

            "name": "sourceFileId",

            "code": "notFound",

            "value": "67f5403f06a6263c897e8aac"

        }

    ]

}

Finally, we could not find any option in the Trados Cloud web interface to manually add a new version to an existing source file, which makes it more difficult to validate the behavior of this endpoint.

 Questions:

  1. What are the exact conditions for a source file to be considered "linked" to a task?
  2. Are there specific criteria or project/task configurations that must be met for the sourceFileId to be accepted?
  3. Is it possible to identify which source file ID is expected by the task through any other API endpoint?
    1. If so, what would be the recommended way to fetch this information?
  4. Is the functionality of adding a new version to a source file available through the Trados Cloud web interface? (We were unable to locate any option that performs this action manually)

 Your insights would be greatly appreciated as we are keen to move forward.



.
[edited by: Paul at 8:34 PM (GMT 1) on 14 Apr 2025]

Paul Filkin | RWS Group

________________________
Design your own training!

You've done the courses and still need to go a little further, or still not clear? 
Tell us what you need in our Community Solutions Hub

Parents
  • Hi Paul,

    I investigated a bit the issue and found some logs related to your requests.

    Here are my reccommendations to your questions: (in an order which I think will make it easier to understand)

    3. You could use https://eu.cloud.trados.com/lc/api-docs/a2c8de9366f24-get-task with ?fields=input.type, this will gine you the information what the spefic tasks takes an input, here by attaching the specific input.sourceFile.id, you also get the relevant input sourceFile/targetFile/project etc identifier.

    2. The input type of the task must be of `sourceFile` for the update to be possible with a new source file version, same is true for tasks with input type `targetFile` versions and tasks which take as input a target file. Form the logs I have seen that you tried to operate on a `human-translation` tasks, which is a tasks which has an input-type of `targetFile`.

    4. Specifically for source file update, you can take as an example the engineering task. Same rules apply, task must be accepted by owner (owner opens it from Inbox), then the owner is able to add a new source file version.

    1.I think this is already anwsered in the previous points. But feel free to follow-up if there are other questions.

    Laszlo

Reply
  • Hi Paul,

    I investigated a bit the issue and found some logs related to your requests.

    Here are my reccommendations to your questions: (in an order which I think will make it easier to understand)

    3. You could use https://eu.cloud.trados.com/lc/api-docs/a2c8de9366f24-get-task with ?fields=input.type, this will gine you the information what the spefic tasks takes an input, here by attaching the specific input.sourceFile.id, you also get the relevant input sourceFile/targetFile/project etc identifier.

    2. The input type of the task must be of `sourceFile` for the update to be possible with a new source file version, same is true for tasks with input type `targetFile` versions and tasks which take as input a target file. Form the logs I have seen that you tried to operate on a `human-translation` tasks, which is a tasks which has an input-type of `targetFile`.

    4. Specifically for source file update, you can take as an example the engineering task. Same rules apply, task must be accepted by owner (owner opens it from Inbox), then the owner is able to add a new source file version.

    1.I think this is already anwsered in the previous points. But feel free to follow-up if there are other questions.

    Laszlo

Children
No Data