https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/en-USTelligent Community 12 Non-Productionhttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60967/assign-task-to-vendor-via-api/193355Thu, 30 Apr 2026 07:10:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:845c3d94-7aa7-46ff-9149-73871f3d57baLaszlo DavidHi Laurent Pierret , it happens to know the root cause of this. `Empty vendorConfig in plannedAssignee for vendorOrderTemplate 69399a61515d7b6bf097d2b6` This means on your Vendor Order Template you must specify managers and assignees for all language directions. Also we will work to improve the error response here too.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60972/task-event-payload-is-missing-the-outcome-property/193354Thu, 30 Apr 2026 07:02:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:80ae73c6-1425-4c24-bae4-5d0e30362139Maria MironHi. CRQ-45463 was raised internally for tracking.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60972/task-event-payload-is-missing-the-outcome-property/193353Thu, 30 Apr 2026 06:55:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:784f8389-a64f-4aaf-b3a4-9efa7654d446Laurent PierretDear Laszlo David , thank you for the update.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60972/task-event-payload-is-missing-the-outcome-property/193352Thu, 30 Apr 2026 06:33:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:31a0c7da-d23c-4a60-8564-c1bd1d457849Laszlo DavidHi Laurent Pierret , thank you for reporting it, we identified a bug in this area. The team will prioritize it and fix it.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60972/task-event-payload-is-missing-the-outcome-propertyTue, 28 Apr 2026 06:39:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ed65bf6c-0720-4953-b1d9-f7fba865f453Laurent PierretDear community, I try to capture task rejections via the PROJECT.TASK.UPDATED. According to the documentation , this event is triggered if a task is rejected. However, since the payload does not contain the outcome property (as described here ), it is not possible to identify from the payload that the event was triggered because the task was rejected (maybe because the task is not finished?). How can I identify the rejection? Thank you in advance for your support. Regards, Laurenthttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60967/assign-task-to-vendor-via-apiMon, 27 Apr 2026 10:25:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:4b3009f9-7165-45a0-8157-e4c5bdea1558Laurent PierretHello, Via the API, I would like to change the assignee of task (human-translation) from a group to a vendor order template. When I try to do so, I do get a 422 response (U nprocessable Entity) with the following error: { "errorCode": "invalid", "message": "Input validation error occurred. No further details available.", "details": [] } What is the reason? Do I need to perform an other step before assigning? Regards, Laurenthttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60828/api-call/192863Mon, 13 Apr 2026 09:32:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0e4e1468-96e2-440b-b363-458913b0eff2Nick DateYou can create a Service User in Users -> Service Users If you can't see this, then you may not have the necessary entitlement. We cannot give this sort of information out on a public forum, so please raise a support case , and we will be happy to help.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60828/api-call/192856Mon, 13 Apr 2026 06:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e5a70805-dff7-4506-b0a8-ba217f9fec0bNzhdeh BarseghyanHi Laszlo David , here is my tenant ID - xxxxxxxxxxxxxxxx. Thank you in advance.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60828/api-call/192807Fri, 10 Apr 2026 10:42:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6a6779c4-c171-44f0-8d42-65b720a31843Laszlo Davidhi Nzhdeh Barseghyan , can you provide some details? account/tenant id?https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60828/api-callWed, 08 Apr 2026 08:49:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:41a30dac-2c1b-4aab-b844-79b84681da32Nzhdeh BarseghyanHi! I am a developer building a standalone automation service using the Trados Public API. I need to set up a Service User for OAuth2 Client Credentials authentication, but I cannot locate the 'Service Users' management area in my current dashboard. Can you please: Point me to the exact location of Service User management for my tenant? Confirm if my current subscription tier supports Public API access and the creation of Service Users? Verify if OCR (Optical Character Recognition) is enabled for my account's file-type configurations so I can analyze JPG/PNG files? Thank you in advance.APIhttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60765/data-bridge-does-not-support-contains-in-filterMon, 30 Mar 2026 07:39:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:aa1a5c4d-5a68-4c65-a758-b6732acc632dLaurent PierretGood morning, Although described here: developers.rws.com/.../OData-Query-Guide.html , the data bridge does not support the "contains" function in filter. See attached screenshot: the error says "Method are not allowed". Thank you for your guidance.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60637/potential-outage-24-25-feb-2026/192150Fri, 20 Mar 2026 12:31:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:76838777-a4c0-4a87-a4fd-fa2cf0977b95Laszlo DavidHi Evgenii: we can see from the logs: 2026-02-24 19:54:11.210 [Calling extension with id intento-routings-bcm-async-automatictask. Sending a POST request to connectors.inten.to/.../bcmtranslate_async but there was no callback received for this task in 4hours, so the task was expiredhttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/59999/potential-outage-at-dec-27th-10-01-22-30-pst/192147Fri, 20 Mar 2026 12:10:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:21164826-f837-485f-84aa-40931605819aLaszlo DavidThe page where outages can be seen is: https://status.cloud.trados.com/https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60637/potential-outage-24-25-feb-2026Thu, 19 Mar 2026 13:07:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:8ccae050-3634-4108-8a73-d0e335108bdeEvgenii SamarinHello RWS team! Our client got an error in workflow tasks. Based on our logs/opentelemetry, there were no requests that we received. Could you please check what happened to the step in the workflow pipeline? Details about the error received: T ask,UNRESPONSIVE,699e01d571231a419a4df3bfhttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60438/how-to-receive-all-fields-of-multiple-termbase-entries-without-exceeding-url-length-limit/191800Fri, 06 Mar 2026 15:47:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:84459599-9d3e-4495-9e88-01e1aa2ad86ePatrick Andrew Hartnetthi Tamas Meszaros , The 414 (Request-URI Too Long) is coming from the practical URL length limit enforced by the web server/proxy in front of the API, so very long fields=... + many humanReadableIds=... parameters will hit that limit. To address the “I just want everything” scenario: we’re currently testing support for a wildcard on the fields parameter (e.g. fields=*) to avoid having to send a very long explicit list. It’s not something we’re ready to officially document/promote yet while we complete validation, but it should help with exactly the use case you described and significantly reduce the URL size. Until this is fully supported/documented, the reliable workaround is to batch the IDs into smaller groups to keep the request URL under the limit. I’ll keep you posted as soon as we can confirm the wildcard is fully supported and ready to be documented. Currently tracking yr feedback here SDLCOM-6725 so that I remember to circle back to you when this is supportedhttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60438/how-to-receive-all-fields-of-multiple-termbase-entries-without-exceeding-url-length-limit/191799Fri, 06 Mar 2026 15:47:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:daf19a59-8590-4289-a28b-f205994c27e2Community JiraThank you for bringing this to our attention. Our development team will review it in the context of our ongoing projects and priorities. Your understanding and patience as we assess this matter is appreciated. We have recorded the issue in our tracking system under the reference number SDLCOM-6725https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60438/how-to-receive-all-fields-of-multiple-termbase-entries-without-exceeding-url-length-limitTue, 24 Feb 2026 13:16:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:38c44ede-594f-4b36-b176-62c6c8e95d3dTamas MeszarosHi, I would like to read several termbase entries through the LC rest API, and I would like to query all fields of them. According to the docu, optional fields are not returned by default, so I have to specify all required fields in the fields parameter. This alone is already very long, ~ 3300 characters: fields=humanReadableId,languages.language.languageCode,languages.language.englishName,languages.terms.text,languages.terms.systemStatus,languages.terms.termbaseFieldValues.termbaseFieldId,languages.terms.termbaseFieldValues.name,languages.terms.termbaseFieldValues.value,languages.terms.termbaseFieldValues.fieldValueLinks.type,languages.terms.termbaseFieldValues.fieldValueLinks.value,languages.terms.termbaseFieldValues.createdAt,languages.terms.termbaseFieldValues.lastModifiedAt,languages.terms.termbaseFieldValues.createdBy.email,languages.terms.termbaseFieldValues.createdBy.firstName,languages.terms.termbaseFieldValues.createdBy.lastName,languages.terms.termbaseFieldValues.createdBy.anonymized,languages.terms.termbaseFieldValues.createdBy.anonymizedUserName,languages.terms.termbaseFieldValues.lastModifiedBy.email,languages.terms.termbaseFieldValues.lastModifiedBy.firstName,languages.terms.termbaseFieldValues.lastModifiedBy.lastName,languages.terms.termbaseFieldValues.lastModifiedBy.anonymized,languages.terms.termbaseFieldValues.lastModifiedBy.anonymizedUserName,languages.terms.createdAt,languages.terms.lastModifiedAt,languages.terms.createdBy.email,languages.terms.createdBy.firstName,languages.terms.createdBy.lastName,languages.terms.createdBy.anonymized,languages.terms.createdBy.anonymizedUserName,languages.terms.lastModifiedBy.email,languages.terms.lastModifiedBy.firstName,languages.terms.lastModifiedBy.lastName,languages.terms.lastModifiedBy.anonymized,languages.terms.lastModifiedBy.anonymizedUserName,languages.termbaseFieldValues.termbaseFieldId,languages.termbaseFieldValues.name,languages.termbaseFieldValues.value,languages.termbaseFieldValues.fieldValueLinks.type,languages.termbaseFieldValues.fieldValueLinks.value,languages.termbaseFieldValues.createdAt,languages.termbaseFieldValues.lastModifiedAt,languages.termbaseFieldValues.createdBy.email,languages.termbaseFieldValues.createdBy.firstName,languages.termbaseFieldValues.createdBy.lastName,languages.termbaseFieldValues.createdBy.anonymized,languages.termbaseFieldValues.createdBy.anonymizedUserName,languages.termbaseFieldValues.lastModifiedBy.email,languages.termbaseFieldValues.lastModifiedBy.firstName,languages.termbaseFieldValues.lastModifiedBy.lastName,languages.termbaseFieldValues.lastModifiedBy.anonymized,languages.termbaseFieldValues.lastModifiedBy.anonymizedUserName,termbaseFieldValues.termbaseFieldId,termbaseFieldValues.name,termbaseFieldValues.value,termbaseFieldValues.fieldValueLinks.type,termbaseFieldValues.fieldValueLinks.value,termbaseFieldValues.createdAt,termbaseFieldValues.lastModifiedAt,termbaseFieldValues.createdBy.email,termbaseFieldValues.createdBy.firstName,termbaseFieldValues.createdBy.lastName,termbaseFieldValues.createdBy.anonymized,termbaseFieldValues.createdBy.anonymizedUserName,termbaseFieldValues.lastModifiedBy.email,termbaseFieldValues.lastModifiedBy.firstName,termbaseFieldValues.lastModifiedBy.lastName,termbaseFieldValues.lastModifiedBy.anonymized,termbaseFieldValues.lastModifiedBy.anonymizedUserName,createdAt,lastModifiedAt,createdBy.email,createdBy.firstName,createdBy.lastName,createdBy.anonymized,createdBy.anonymizedUserName,lastModifiedBy.email,lastModifiedBy.firstName,lastModifiedBy.lastName,lastModifiedBy.anonymized,lastModifiedBy.anonymizedUserName The problem is that if I would like to specify e.g. 20 entry IDs like humanReadableIds=LC6570452991d6c955906daf37&humanReadableIds=LC65707c7082468403c1f9e318&humanReadableIds=LC65707cf5edee745afa957d55&humanReadableIds=LC65707e3082468403c1f9e509&humanReadableIds=LC65707f0382468403c1f9e6de&humanReadableIds=LC657081c1edee745afa98b06d&humanReadableIds=LC6570821682468403c1fd023d&humanReadableIds=LC65708372edee745afa9a787e&humanReadableIds=LC657084e582468403c1fff69a&humanReadableIds=LC657086ec82468403c1015b43&humanReadableIds=LC657087e2edee745afa9cd67a&humanReadableIds=LC657094a0edee745afaadb66b&humanReadableIds=LC65719422edee745afaf41032&humanReadableIds=LC6571958aedee745afaf420dd&humanReadableIds=LC6571962982468403c14c177c&humanReadableIds=LC65719678edee745afaf42829&humanReadableIds=LC6571972cedee745afaf43a28&humanReadableIds=LC6571998bedee745afaf9d717&humanReadableIds=LC65719b8082468403c15526e6&humanReadableIds=LC65719e2dedee745afaf9ed34 then I already get an error like 414 (Request-URI Too Long) ~ the complete GET query is 4275 characters long. Is there a trick maybe reduce the length? It seems to be kind of waste to use 3300 characters just to express that I would get everything, and having to increase the API calls just because too few space remains for the IDs. E.g. wildcards would be perfect to use, but AFAIK they are not supported. thanks, Tamashttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/59999/potential-outage-at-dec-27th-10-01-22-30-pst/191040Fri, 06 Feb 2026 16:18:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4667698-5954-4b58-bd37-9c143fd17bcbEvgenii SamarinHello! We had no such logs, but do you have any information about the potential outage? Do you have a status page where we can track such events?https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60204/how-to-uplad-perfect-match-files-to-the-cloud/190894Fri, 30 Jan 2026 09:08:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c1456127-7dfa-4505-9e4f-ddecc7f83903Rares TriteanYes, please open a ticket IF creating a mapping with the example I've provided does not work.https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60204/how-to-uplad-perfect-match-files-to-the-cloud/190890Fri, 30 Jan 2026 08:28:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:255185af-9425-4195-86db-83190a7c1933AndréSounds like a plan This is the trace id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx EDIT: The ID is always replaced. How can i provide it? Via Ticket?