A related asset is any Sanity document referenced by the document you are requesting for translation. Related assets are not automatically included in a translation request — you must explicitly select a Related Assets depth when requesting translation.

If a referenced document has never been translated, the parent page may still show source-language content in the sections that come from that reference, even after the parent document itself is fully translated.

No. Connector-side updates do not require any plugin updates in Sanity Studio. You only need to re-request affected documents via the Smartling dashboard. The sanity-plugin-smartling plugin is only required for schema export and does not need to be updated when the connector backend changes.

No. If the source content has not changed and translations were saved to the translation memory, SmartMatch can be used to match the strings automatically. Re-requesting documents is safe and is recommended for bulk recovery workflows.

Re-request the document from the Sanity tab. If you added new references, re-request with Related Assets (Level 1 minimum). Strings that have already been translated and saved to the translation memory can SmartMatch at no additional cost.

Important: Always use the Sanity (Documents) tab in the Smartling dashboard to request or re-request translations. Do not use the Strings View or the Jobs Dashboard to request translations— these do not update the connector's tracking state.

1. Open the Sanity tab in your Smartling project.
2. Filter by Content Type (e.g., productDetailList).
3. Click "Select all matching current filter".
4. Under the Actions menu select "Request Translation" and choose the related assets depth as appropriate.

A Failed status means an error occurred during file ingestion or delivery. Open the document's detail view in the Smartling dashboard to check the specific error details.

The connector uses the preview.select.title field from your document schema to name files in Smartling. Common causes of "Untitled" files:

• The schema has an empty preview block ("preview": {})
• The preview.select.title field is not defined
• The title resolves to an object instead of a string — use dot notation (for example, "title": "titleLocalization.eu_store" instead of "title": "titleLocalization")
• The title path references a nested field that only exists on a sub-document, not on the top-level document

The file URI in Smartling is set at first upload and is never updated. To find a file after a title change, search by the document ID (not the title). The file URI always contains the document ID.

There are several possible causes: 

The document is not yet complete in Smartling. Open the Sanity tab in your project and check the status of the document. If the status is anything other than Completed (for example, In Progress or Failed), the translation has not been delivered.

Specific strings were not ingested from Sanity. If the document is completed but a particular string is still in the source language, the string may not have been ingested for translation. Check if the content exists in Smartling. If it does not, review your Content Parsing settings. 

A parent document was not requested. Some content is structured hierarchically in Sanity. If only a child document was requested, the parent document's reference may not have been updated. Check the direct parent document and its status in the Smartling Sanity tab.

A referenced document (related asset) was never requested. Check the translated locale copy — if a field contains a reference, the referenced document must also be translated.

The frontend is rendering the source-language document. If the locale copy in Sanity contains the correct translation but the page still shows source-language content, the issue could be due to frontend rendering, not the connector. 

The translated document has not been published in Sanity. Verify the document's publish status in Sanity Studio. Depending on your delivery strategy, the connector may deliver translations as drafts rather than published documents.

Step-by-step troubleshooting

1. Identify the document. Find the Sanity document ID for the content that still shows in the source language.
2. Check the document status in the Sanity tab of your Smartling project. If the status is anything other than Completed, that is the problem. Completed status means the connector delivered the translations successfully. Resolve any errors before proceeding.
3. Check the document strings. If the document is completed but the specific string is not present in Smartling, this is a content parsing issue — the string was never ingested from Sanity.
4. Verify the locale copy. If the status is Completed but the content still shows in the source language, open the locale copy in Sanity Studio or via the Sanity API. If the locale copy contains the correct translation, this is a frontend rendering issue, not a connector issue. Check which document ID the frontend is referencing.
5. Check related assets. The issue may be in a referenced document, not the root document. In the Smartling Sanity tab, open the root document and look for related assets with no Last Requested date. You can also inspect referenced document IDs directly in Sanity Studio or via the API.
6. Re-request the root document with Related Assets from the Sanity tab. Be sure to request the content for translation using the Sanity tab in the project. Do not use the Strings View or the Jobs Dashboard, as this does not update the connector's tracking state. The connector will not be aware of any translation requests made outside the standard Sanity tab request translation flow. 

Note: Requesting a child asset alone will not update the parent document's reference. Always re-request the parent document as well.