In order to troubleshoot technical issues or to identify translations for quality purposes, we may ask you to send us a unique identifier for any given conversation or message.

Each Knowledge record is identified with a unique ID corresponding to a Salesforce standard format - ex: ka0KA000000XemHYAS. The easiest way to capture this ID is to navigate to the original article and copy the URL, which should look something like https://unbabeldemo1-dev-ed.lightning.force.com/lightning/r/Knowledge__kav/ka0KA000000XemHYAS/view.

Each translated version of the article will contain a unique ID of its own. There is a parent-child relation concerning these records: a translation of an article will have as its parent ID the unique ID of the original article.

You can also check for translation requests in the Translation Request record view. To access it, open the app launcher and search for Translation Requests.

The Translation Requests view allows you to search all current and previous requests made in the organization, as well as filtering for status, creation date, etc. It also allows to quickly retrieve the identifiers.

If you need to share a problem with a translation, usually it will be enough to share the ID of the original article, the ID of the translation, the language affected, and the date/time of the request.

However, under certain circumstances, we may ask for a full report on Translation Requests, in order to obtain a detailed file containing information on all Unbabel requests generated on your organization, their properties and check for possible errors or patterns. The report can also be used to monitor different metrics like translation statuses, translation types, delivery times, language pairs and errors handling.

You can find the guide on how to report on TRs in this article.