The release notes summarize the changes introduced over the previous week.
New Features & Improvements
- Machine translation and Auto Adapt now respect <notranslate> and [NOTRANSLATE] markup, so wrapped content such as code blocks, placeholders, and protected terms is no longer translated or altered during fluency adjustments
- Added a Quality vs Latency preference option for Google Translate engine
- The segments API now returns each segment's translation origin (translation memory, machine translation, or no-translate), match score, and confirmed/locked status
- The language assets search API now returns richer term base metadata — part of speech, usage notes, definitions, and more — for each matched term
- Strings API rate-limit responses now include an X-Rate-Limit-Reason header indicating whether the limit was hit due to request concurrency or request rate
- Added import and export support for the Fluent (.FTL) localization file format, including variable interpolation and plural expressions
- Phrase Studio no longer requires a separate "connect" step — entitled users are automatically provisioned and taken directly into Studio
Bug Fixes
- Fixed: TMS job pre-translate using the AI Translation Agent now applies the project's linked content group style guide rules
- Fixed: the file translations API rejected term base configuration for translation profiles that don't use the AI Translation Agent engine, even though their engines support term bases
- Fixed: filtering translation memory content search by project could return zero results even though the project had matching content
- Fixed: searching across translation memories with certain regular expressions could incorrectly show an "Illegal repetition" error
- Fixed: the translation memory content search key-name filter didn't match automatically generated context keys for ICU plural sub-messages
- Fixed: linking a style guide rule to a different content group could incorrectly unlink it from its style guide, even when the change didn't affect the style guide association
- Fixed: Orchestrator trigger filters using the "equals" comparator could fail to match values containing special characters such as "+" or ".", for example usernames that include a "+"
- Fixed: the "Assign providers from template" dialog showed help text that was cut off mid-sentence
- Fixed: running Update Source twice at the same time on the same job could create duplicate records; concurrent requests are now rejected with a clear error instead
- Fixed: saving project import settings could fail with an invalid URL error when the URL was one generated internally by Phrase
- Fixed: the Figma plugin could show a false "in-context editing unavailable" message for accounts that do have access
- Fixed: updating a job through the API could return a confusing 404 error when a "branch" value was included in the request body
- Fixed: Global Search's "View all results" link didn't open in a new tab when using middle-click or Ctrl-click, instead duplicating the current job tab
- Fixed: Strings Job Sync could create empty translation segments in TMS for plural keys where every plural form was empty
- Fixed: project duplication could get stuck indefinitely if a locale-copy step needed to retry
- Fixed: "Sync to TMS" in Phrase Studio could discard translated edits by triggering a full reimport instead of updating the existing translation
- Improved timeline zoom performance for long recordings in the Speakers view
- Fixed: the Tridion connector could hang indefinitely when listing or downloading files, which could block Automated Project Creation for extended periods
- Fixed: Automated Project Creation could stop checking for new files after a failed file lookup delaying imports
- Fixed: Braze Multilang file downloads returned a generic server error instead of a clear error when the source locale was missing
- Fixed: comments added to a segment in bilingual DOCX export could be duplicated onto sibling segments created by splitting the same source paragraph
- Fixed: new users could see an unclear error or a stuck screen when finishing sign-up; validation errors are now shown clearly instead of failing silently
- Fixed: the sort-direction arrow on the Users table's User column didn't update when the sort order changed
- Fixed: bot accounts were sometimes incorrectly flagged as needing two-factor authentication, and could still appear when filtering for non-compliant members
- Fixed: social sign-in could fail with a database error when the session identifier was too long
- Fixed: Atlas-created Orchestrator workflows could reference a translation project incorrectly, causing automated post-editing analysis actions to fail
- Fixed: Atlas could misreport segment confirmation status when comparing workflow steps
- Fixed: Atlas conversations sometimes had no chat name generated
- Fixed: Atlas conversations could end abruptly during a deployment without any notice to the user
- Fixed: Atlas could clear a project template's owner field when updating it through certain API versions
- Fixed: Advanced Analytics could show an incorrect due date for workflow steps due to a timezone conversion issue