Weekly Release Notes

Weekly Release Notes — October 5, 2026

The release notes summarize the changes introduced over the previous week.

New Features & Improvements

  • Storyblok plugin can now trigger translation directly from a story, publish translations through Storyblok Releases, and show a ready-to-publish status in the story view
  • Automated Project Creation (APC) configurations now appear in the TMS Recents list
  • Automated Project Creation (APC) owners can be notified by email and in-app when an APC needs attention (e.g. a failed export), in addition to the existing stopped notification
  • New webhook events are available in Strings for linked keys: key_links:create and key_links:delete

Bug Fixes

  • Fixed: deleted machine translation profiles could remain selectable in Project Settings
  • Fixed: Quality Evaluation runs could silently complete with no result for tasks that actually had content to review
  • Fixed: Translation Memory search results could show target-language text in the Source column
  • Fixed: clicking a segment in a Translation Memory could open the wrong segment's details when the source language also appeared as a target language
  • Fixed: Translation Memory content search project filter didn't match translation units whose project was stored by name rather than numeric ID
  • Fixed: a field-name mismatch could prevent the "Active rule limit reached" error from appearing during bulk rule enablement
  • Fixed: Test Connection could validate a connector's previously saved configuration instead of the values currently shown in the form
  • Fixed: an already-authorized OAuth2 connection could incorrectly show "Not authorized" on edit
  • Fixed: APC export/import jobs could fail with a generic error during a transient backend outage instead of retrying automatically
  • Fixed: target languages added to an already-running APC project could never have their translated jobs marked Delivered or pushed to Phrase Strings
  • Fixed: an APC could get stuck permanently in "Running" when a connector never responded to change detection
  • Fixed: an HTML filter issue that could truncate image URLs when the query string contained the text "alt="
  • Fixed: the Jobs view's infinite scroll could stop loading new groups, or silently skip entire groups, when grouped by Filename, Status, Job owner, or Project
  • Fixed: the structure tag icon in the Jobs view table was not vertically centered
  • Fixed: incorrect pluralization in the "My connectors" pagination footer when there was exactly one connector
  • Fixed: adding one target language to a project could rewrite every target-language row instead of only the new one
  • Fixed: multi-target-language batch job creation from a multilingual XLS/CSV/XML file could intermittently drop a target column
  • Fixed: users could be blocked from creating a project template that referenced a file uploaded by another member of their own organization
  • Fixed: PO Gettext exports with "Override PO header" enabled could produce a duplicate header line when the source value was blank
  • Fixed: some accounts with Modify Users permission or Administrator role could be blocked from saving any change to a user profile that had clients assigned
  • Fixed: Term Base CSV download modal in Strings showed two duplicate "Download" buttons
  • Fixed: the iOS .strings file importer in Strings could turn single-line comments containing "=" into bogus extra keys instead of key descriptions 
  • Fixed: XLIFF uploads to Strings could fail with a generic error when "ignore target translations" was enabled and the file had no source-language attribute
  • Fixed: Translators granted per-project PM rights could get an error when searching or adding project members in Strings
  • Fixed: the screenshot creation API could return an unhelpful empty error instead of a descriptive validation message
  • Fixed: a project keys table could break its layout when a key name contained very long or embedded content
Was this article helpful?
★ ★ ★ ★ ★

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.