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/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/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-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-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?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/190889Fri, 30 Jan 2026 08:15:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:783c9e7d-2378-49de-832c-b22b15e44c12Rares TriteanHi, When creating a new Perfect Match Mapping you should be able to only send the projectId that the mapping will be associated to, i.e: your not started project 6970fa5993d3cd12124d7bbe: { "projectId": "6970fa5993d3cd12124d7bbe" } If this step fails, please provide us with a TraceID so we can investigate this further. Let's unblock this first step then we can continue with the rest of the flow. - Rares.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/190857Wed, 28 Jan 2026 13:40:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c7ed9a89-b51d-4860-94eb-928e557e0ceaAndréHi Rares, thanks for your reply. My first attempt was to upload the sdlxliff files for PerfectMatch via the Add Source File endpoint. But I think this is the wrong way. After that I tried to create a Perfect Match Mapping . My body looks like this: { "projectId" : "6970fa5993d3cd12124d7bbe" , "matchingProjects" : [ "6970e3e69e57314fefbc15b5" ] } I also tried it without matchingProjects (because I dont want to use other projects for Perfect Match) but I always get this as response: { "errorCode" : "invalid" , "message" : "Input validation error occurred. No further details available." , "details" : [] } The project with id 6970fa5993d3cd12124d7bbe is not started. Without mappingid I cannot use any of the other Perfect Match endpoints. So right now, I am stuck. What am I doing wrong?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/190838Wed, 28 Jan 2026 08:50:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:59bd83e6-5265-4edf-88bf-85ba919658faRares TriteanHi, The Perfect Match Mapping flows are detailed in the official documentation . When working with the Trados Cloud API, you may use the Create Perfect Match Mapping endpoint to create a new one, then Perfect Match should work automatically if conditions above are met. If you need to provide your own files as sources to match against, you can use this endpoint to upload your files. If your project is already started, and you upload new source files, that is considered a new Batch, so creating a new Perfect Match Batch Mapping associated with your project is a must. Can you please provide more details about your specific use-case? It will help us provide the correct assistance. Thank you, Rares.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-cloudMon, 26 Jan 2026 15:04:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:becae298-ce19-4a3b-b4a0-8456601ed75bAndréWe recently started using the Trados Cloud platform. I am trying to upload the Perfect Match files (.sdlxliff) via the REST API. Creating a project and uploading the files (via API) works, but Perfect Match is then skipped in the workflow for the files. Unfortunately, the API reference does not provide quite as much information as it should for the whole thing to work. I upload the files using the “Add Source File” endpoint: api.eu.cloud.trados.com/.../v1 /projects/{projectId}/source-files The question is, what exactly should the properties look like? Currently, they look like this: var bilingualUploadProps = Newtonsoft.Json.JsonConvert.SerializeObject(new { name = sdlxliffname, role = "reference", type = "sdlxliff", language = sourceLanguageShort }); Are role and type correct? Unfortunately, that doesn't seem to be enough. Do I now have to create a “PerfectMatch Mapping” using the API? If so, how do I do that for the .sdlxliff files? By default the PerfectMatch Mapping want to have "matchingProjects" but we don't have these yet. We want to use the older sdlxliff files. Thanks for the help.UploadCloud projectRest APISDLXLIFFTrados TeamPerfectMatchhttps://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/190650Tue, 20 Jan 2026 08:34:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:02342b99-8c47-4149-afee-13223e4ca801Laszlo DavidEvgenii Samarin Luca De Franceschi , please provide details, tenantId, projectId, start request timestamp, I need this details to be able to do a targeted investigation. Please see eu.cloud.trados.com/.../how-to-report-an-issuehttps://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60105/how-to-retrieve-a-project-s-current-and-future-tasks/190649Tue, 20 Jan 2026 08:11:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:fca93bfd-01a2-41c9-b155-d4139b3f9260Henk HendriksHi Laszlo, Thanks! That does indeed work. Best regards, Henkhttps://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/190624Mon, 19 Jan 2026 11:39:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c0d7722a-060b-4694-9db3-980ab39e8c89Evgenii SamarinHello! A bit of context here: the problem is that our client did start the translation workflow, but we haven't received the request on our side during the specified time period. Can you confirm that there was an Intento Translate step in the workflow queue that is not called via API?https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60105/how-to-retrieve-a-project-s-current-and-future-tasks/190578Fri, 16 Jan 2026 10:06:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:fe689866-ad19-4871-938d-a83ba286a814Laszlo Davidplease try the https://eu.cloud.trados.com/lc/api-docs/fd9ee0beb37ca-get-project with field projectPlan.taskConfigurations. description states: The configurations of the tasks that will be created in the future. Available now directly after project creation, project does not need to be started to be populated. This is enough to be retrieved once per project, (assuming the initial request of [quote userid="3666" url="~/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/60105/how-to-retrieve-a-project-s-current-and-future-tasks"]field project.workflow.taskConfigurations [/quote] was on task level (this is redundant, and will do multiple unneccessary calls)https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/59953/clarification-on-api-status-messages-for-canceled-vs-error-files/190572Fri, 16 Jan 2026 08:25:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:59c6d339-27c5-4dab-9056-6bde040fd14eLaszlo DavidLuciana Scocco , can you please elaborate more in detail, what operations are you doing with tasks thath still surface "error". Could you give traceIds, specific endpoint calls? (method+url) Are you using plain htpp or SDK?https://community.rws.com/developers-more/trados-portfolio/language-cloud-developers/f/language_cloud_sdkapi_qa/59953/clarification-on-api-status-messages-for-canceled-vs-error-files/190571Fri, 16 Jan 2026 08:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:bbc8b65c-46d2-49e3-8efa-2f09275efa27Luciana ScoccoHi Laszlo David , Thanks for the details. Our concern is that, after a file is canceled, the API responses we receive for tasks still surface “error” details without a clear, consistent way to detect that the underlying file (or target) was canceled. In practice, this leads TRT to treat canceled items as errors, which breaks downstream handling (e.g., target retrieval logic). Could you confirm a reliable indicator we can use—via the tasks or target-file endpoints—to distinguish: Canceled vs. Error states, and Ensure canceled items don’t surface only as task “errors”? Thanks,