Idea Delivered

Queue function in "File Delivery" to avoid errors (connector projects)

Idea: Include a queue function / delay automatism before "File Delivery" task to avoid errors and manual work.

Situation:
We often experience the situation that "File Delivery" tasks fails in SFTP connector projects if many files are completed at the same time.
While this also happens with other tasks where the issue can usually be solved by "retry", this is not possible for file delivery. Here, it leads to an email error message which lets you know which file failed but not the target language, so we usually end up downloading and pushing all files manually to SFTP again.

An integrated queue function/ delay / release interval before the "File Delivery" task would hopefully help to prevent those errors and save the manual work.
(interval: a few seconds? to be tested)
Error message displayed for Automatic Connectors with text 'Error encountered' and details including timestamp, trace ID, and failed file upload information.

(@RWS, see also support case CS0005514)

Evelyn Hoffmann

  • Hi Evelyn,

    I received a further update from the Connectors team this morning to advise me of the following:

    To address the file delivery issue, we’ve implemented a re-integration mechanism that automatically triggers whenever such collisions occur. With this mechanism, the system will re-download the translated file from Trados and attempt to push it to the target folder again. Additionally, we’ve added retry logic to ensure the system automatically reattempts delivery in case of a failure.

    Can you please monitor for any reoccurrences of this issue following the update that has been deployed, and report the details via a support ticket in the event you see any new examples?

    Cheers,

    Ian 

  • Hi Evelyn, 

    I discussed this with the team responsible for connectors in Trados who confirm they are aware of the issue. It appears this only occurs in a scenario where two files from the same project attempt to reintegrate simultaneously - whether that be to SFTP or a different type of connector.

    A fix has been developed and is currently being tested. The team hope this will be deployed to Production in the near future.

    Cheers,

    Ian