#Smartling app changelog

#August 2026

Improvements

Sort entries by when they were last updated: The Smartling view now sorts entries by most recently updated by default, so content that changed since your last translation round appears first. A SORT BY control lets you switch to least recently updated, or back to the previous ID ordering.

#July 2026

Improvements

Filtering by title on models with a fixed set of title values: When a model's title field is an enum, the Smartling view now shows a TITLE dropdown listing that enum's values, so those models can be filtered by title instead of offering a free-text search that might never match.
Warning for long-running syncs: Selecting a large number of locales for a single sync can push the import close to timing out. The sync dialog now shows a warning when an import has been running unusually long, suggesting you split the work into smaller batches.
Clearer message when the Content API token has expired: An expired or unauthorized Content API token previously surfaced as a generic unknown error while loading entries or running Smartling actions. The app now states that the Content API token has expired or failed authentication, so you can update it and retry.
Content API errors are shown instead of hidden: When the Content API rejects a request while loading entries, the app now shows what the Content API actually reported rather than a generic error.

Fixes

Sync failing silently for entries with many locales and rich text list fields: Syncing an entry that combined several rich text list items with many locales could generate a single oversized request that the platform rejected outright, silently dropping the whole conversion step. Large conversions are now split into smaller requests, so syncs of this size complete successfully.
Search by Title failing with an unknown error: On models whose title field is not a single-line text field, or that have no title field at all, searching by title returned no results and showed an UNKNOWN_ERROR message even though matching entries were visible. Title search is now offered only in the form each model supports, such as free text, a value dropdown, or not at all. Where it is not possible, the search box is disabled and the app points you to Search by ID instead; locale and locale status filters continue to work as usual.
Multi-value text translations lost during import: When syncing completed translations back from Smartling, fields holding a list of text values (for example, option lists or tag lists) could come back untranslated, with the translated values dropped without any warning. These list translations are now imported correctly.
Failed syncs reported as successful: When Hygraph rejected an entry update or a localized asset upload during import, for example because of a schema or locale mismatch, the entry was still counted as successfully synced and marked as translated. Such entries now appear in the failed-entries alert instead, so you can see and retry what actually failed.

#June 2026

Fixes

Copying entry IDs when clipboard access is blocked: Copying an entry ID could fail silently in embedded app contexts where browser permissions block direct clipboard writes. The app now falls back to a compatible copy method, and shows an error if copying still cannot complete.
Localized asset uploads for draft-only entries: Importing completed translations could update localized asset text but leave the images themselves pending, because the app looked for asset upload information outside the draft stage or reused localization state across assets in the same gallery. Asset uploads now use draft entry data and evaluate each asset separately, so translated images are re-uploaded during sync.

#April 2026

Fixes

Draft entries could not be submitted for translation: Submitting entries that existed only as drafts could fail before upload because the app prepared an empty Smartling batch. Draft entries can now be submitted reliably, and empty batches are no longer sent.
Setup screen stuck on Saving: On the app setup screen, saving could stay in a loading state indefinitely even after the configuration had been applied successfully, so there was no confirmation and a reload was needed to verify the changes. Saving now completes and confirms reliably.
Missing assets after import for list-based content blocks: Translated entries using list fields that contained only referenced assets could come back with those lists empty, even though the original entry had assets selected. The export and import flow now preserves direct asset references in list fields, so translated entries keep their media.

#March 2026

Fixes

Translations rejected for list fields containing rich text: When syncing translations back from Smartling, list fields whose items contain rich text sub-properties were sent to Hygraph with Smartling metadata still attached. Hygraph rejected the payload and the update failed without a visible error. Translation import now unwraps this nested metadata before updating the entry.

#February 2026

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations: While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect: Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs: Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#January 2026

Fixes

Empty Smartling jobs when title field API ID was missing: Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync: In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs: Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models: Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items: Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#November 2025

Improvements

Clear section and field context in Smartling exports: With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets: When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage: Entries now export with all nested components and Rich Text content included.
Accurate filter counts: Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling: Empty asset arrays within component arrays no longer cause Smartling import errors.

#October 2025

Improvements

Asset translation support: You can translate assets directly.
Smartling job updates: When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation: Rich text fields in both basic and modular components are translated.

#September 2025

Improvements

Stale translation detection: Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation: Edit links for entries open in a new tab for a smooth workflow.
Support for modular components: Fixed issues that previously caused crashes during import or export.
Better error handling: Clearer messages help you troubleshoot issues faster.

#November 2024

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

#Smartling app changelog

#August 2026

Improvements

Sort entries by when they were last updated: The Smartling view now sorts entries by most recently updated by default, so content that changed since your last translation round appears first. A SORT BY control lets you switch to least recently updated, or back to the previous ID ordering.

#July 2026

Improvements

Filtering by title on models with a fixed set of title values: When a model's title field is an enum, the Smartling view now shows a TITLE dropdown listing that enum's values, so those models can be filtered by title instead of offering a free-text search that might never match.
Warning for long-running syncs: Selecting a large number of locales for a single sync can push the import close to timing out. The sync dialog now shows a warning when an import has been running unusually long, suggesting you split the work into smaller batches.
Clearer message when the Content API token has expired: An expired or unauthorized Content API token previously surfaced as a generic unknown error while loading entries or running Smartling actions. The app now states that the Content API token has expired or failed authentication, so you can update it and retry.
Content API errors are shown instead of hidden: When the Content API rejects a request while loading entries, the app now shows what the Content API actually reported rather than a generic error.

Fixes

Sync failing silently for entries with many locales and rich text list fields: Syncing an entry that combined several rich text list items with many locales could generate a single oversized request that the platform rejected outright, silently dropping the whole conversion step. Large conversions are now split into smaller requests, so syncs of this size complete successfully.
Search by Title failing with an unknown error: On models whose title field is not a single-line text field, or that have no title field at all, searching by title returned no results and showed an UNKNOWN_ERROR message even though matching entries were visible. Title search is now offered only in the form each model supports, such as free text, a value dropdown, or not at all. Where it is not possible, the search box is disabled and the app points you to Search by ID instead; locale and locale status filters continue to work as usual.
Multi-value text translations lost during import: When syncing completed translations back from Smartling, fields holding a list of text values (for example, option lists or tag lists) could come back untranslated, with the translated values dropped without any warning. These list translations are now imported correctly.
Failed syncs reported as successful: When Hygraph rejected an entry update or a localized asset upload during import, for example because of a schema or locale mismatch, the entry was still counted as successfully synced and marked as translated. Such entries now appear in the failed-entries alert instead, so you can see and retry what actually failed.

#June 2026

Fixes

Copying entry IDs when clipboard access is blocked: Copying an entry ID could fail silently in embedded app contexts where browser permissions block direct clipboard writes. The app now falls back to a compatible copy method, and shows an error if copying still cannot complete.
Localized asset uploads for draft-only entries: Importing completed translations could update localized asset text but leave the images themselves pending, because the app looked for asset upload information outside the draft stage or reused localization state across assets in the same gallery. Asset uploads now use draft entry data and evaluate each asset separately, so translated images are re-uploaded during sync.

#April 2026

Fixes

Draft entries could not be submitted for translation: Submitting entries that existed only as drafts could fail before upload because the app prepared an empty Smartling batch. Draft entries can now be submitted reliably, and empty batches are no longer sent.
Setup screen stuck on Saving: On the app setup screen, saving could stay in a loading state indefinitely even after the configuration had been applied successfully, so there was no confirmation and a reload was needed to verify the changes. Saving now completes and confirms reliably.
Missing assets after import for list-based content blocks: Translated entries using list fields that contained only referenced assets could come back with those lists empty, even though the original entry had assets selected. The export and import flow now preserves direct asset references in list fields, so translated entries keep their media.

#March 2026

Fixes

Translations rejected for list fields containing rich text: When syncing translations back from Smartling, list fields whose items contain rich text sub-properties were sent to Hygraph with Smartling metadata still attached. Hygraph rejected the payload and the update failed without a visible error. Translation import now unwraps this nested metadata before updating the entry.

#February 2026

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations: While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect: Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs: Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#January 2026

Fixes

Empty Smartling jobs when title field API ID was missing: Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync: In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs: Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models: Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items: Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#November 2025

Improvements

Clear section and field context in Smartling exports: With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets: When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage: Entries now export with all nested components and Rich Text content included.
Accurate filter counts: Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling: Empty asset arrays within component arrays no longer cause Smartling import errors.

#October 2025

Improvements

Asset translation support: You can translate assets directly.
Smartling job updates: When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation: Rich text fields in both basic and modular components are translated.

#September 2025

Improvements

Stale translation detection: Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation: Edit links for entries open in a new tab for a smooth workflow.
Support for modular components: Fixed issues that previously caused crashes during import or export.
Better error handling: Clearer messages help you troubleshoot issues faster.

#November 2024

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

#Smartling app changelog

#August 2026

Improvements

Sort entries by when they were last updated: The Smartling view now sorts entries by most recently updated by default, so content that changed since your last translation round appears first. A SORT BY control lets you switch to least recently updated, or back to the previous ID ordering.

#July 2026

Improvements

Filtering by title on models with a fixed set of title values: When a model's title field is an enum, the Smartling view now shows a TITLE dropdown listing that enum's values, so those models can be filtered by title instead of offering a free-text search that might never match.
Warning for long-running syncs: Selecting a large number of locales for a single sync can push the import close to timing out. The sync dialog now shows a warning when an import has been running unusually long, suggesting you split the work into smaller batches.
Clearer message when the Content API token has expired: An expired or unauthorized Content API token previously surfaced as a generic unknown error while loading entries or running Smartling actions. The app now states that the Content API token has expired or failed authentication, so you can update it and retry.
Content API errors are shown instead of hidden: When the Content API rejects a request while loading entries, the app now shows what the Content API actually reported rather than a generic error.

Fixes

Sync failing silently for entries with many locales and rich text list fields: Syncing an entry that combined several rich text list items with many locales could generate a single oversized request that the platform rejected outright, silently dropping the whole conversion step. Large conversions are now split into smaller requests, so syncs of this size complete successfully.
Search by Title failing with an unknown error: On models whose title field is not a single-line text field, or that have no title field at all, searching by title returned no results and showed an UNKNOWN_ERROR message even though matching entries were visible. Title search is now offered only in the form each model supports, such as free text, a value dropdown, or not at all. Where it is not possible, the search box is disabled and the app points you to Search by ID instead; locale and locale status filters continue to work as usual.
Multi-value text translations lost during import: When syncing completed translations back from Smartling, fields holding a list of text values (for example, option lists or tag lists) could come back untranslated, with the translated values dropped without any warning. These list translations are now imported correctly.
Failed syncs reported as successful: When Hygraph rejected an entry update or a localized asset upload during import, for example because of a schema or locale mismatch, the entry was still counted as successfully synced and marked as translated. Such entries now appear in the failed-entries alert instead, so you can see and retry what actually failed.

#June 2026

Fixes

Copying entry IDs when clipboard access is blocked: Copying an entry ID could fail silently in embedded app contexts where browser permissions block direct clipboard writes. The app now falls back to a compatible copy method, and shows an error if copying still cannot complete.
Localized asset uploads for draft-only entries: Importing completed translations could update localized asset text but leave the images themselves pending, because the app looked for asset upload information outside the draft stage or reused localization state across assets in the same gallery. Asset uploads now use draft entry data and evaluate each asset separately, so translated images are re-uploaded during sync.

#April 2026

Fixes

Draft entries could not be submitted for translation: Submitting entries that existed only as drafts could fail before upload because the app prepared an empty Smartling batch. Draft entries can now be submitted reliably, and empty batches are no longer sent.
Setup screen stuck on Saving: On the app setup screen, saving could stay in a loading state indefinitely even after the configuration had been applied successfully, so there was no confirmation and a reload was needed to verify the changes. Saving now completes and confirms reliably.
Missing assets after import for list-based content blocks: Translated entries using list fields that contained only referenced assets could come back with those lists empty, even though the original entry had assets selected. The export and import flow now preserves direct asset references in list fields, so translated entries keep their media.

#March 2026

Fixes

Translations rejected for list fields containing rich text: When syncing translations back from Smartling, list fields whose items contain rich text sub-properties were sent to Hygraph with Smartling metadata still attached. Hygraph rejected the payload and the update failed without a visible error. Translation import now unwraps this nested metadata before updating the entry.

#February 2026

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations: While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect: Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs: Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#January 2026

Fixes

Empty Smartling jobs when title field API ID was missing: Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync: In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs: Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models: Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items: Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#November 2025

Improvements

Clear section and field context in Smartling exports: With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets: When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage: Entries now export with all nested components and Rich Text content included.
Accurate filter counts: Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling: Empty asset arrays within component arrays no longer cause Smartling import errors.

#October 2025

Improvements

Asset translation support: You can translate assets directly.
Smartling job updates: When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation: Rich text fields in both basic and modular components are translated.

#September 2025

Improvements

Stale translation detection: Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation: Edit links for entries open in a new tab for a smooth workflow.
Support for modular components: Fixed issues that previously caused crashes during import or export.
Better error handling: Clearer messages help you troubleshoot issues faster.

#November 2024

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.