This page shows items released so far this month.
Monday, September 21, 2026 - Version 2026.3.13.0 Azure-EU Azure-US Switzerland
New Editing a Confirmed Translation Resets Its Status to Neutral
When you edit the text of a target language that is Confirmed (green), that language's status now resets to Neutral (gray), so the new wording has to be re-confirmed before it counts as done. Only the edited target language resets; the segment's other target languages and the source text are untouched. If you deliberately set a status in the same action, your status wins and nothing is overridden behind your back. There is no setting and no opt-out: this is the default for everyone, and it applies when you edit in the editor and when you call the segment update method in the API directly. The classic editor is unchanged, repeats updated by auto-propagation follow the same rule, and batch actions, find and replace, and imports are unaffected.
Editor, Translators - WM-27124
New Get the Jobs Linked to Project Files in a Single Call
Integrators can now retrieve, in one call, the jobs each file of a project belongs to, instead of asking Wordbee once per job. Send a project and a list of file IDs, and get back, for each file, the jobs covering it with their target language and status. Every job the caller may see is listed whatever its status, so filtering stays the caller's choice, and a file with no visible jobs returns an empty list rather than an error. The new endpoint is additive, so no existing endpoint changes behavior. One related access correction ships with it: the job word counts list no longer returns rows for clients a restricted user is not assigned to.
API, Administrators - WM-27406
New Editor v2 Is Now Available to Editor v1 Users
Editor v2 is faster and more customizable: infinite scroll, dockable panels, resizable columns, a collapsible segment toolbar that gives the grid more room for text, a dark mode, a live statistics panel, separate finders for translation memory and terminology, a QA panel that checks several documents at once, and a live preview of Word documents. Filtering is stackable and AI-assisted, and an AI translation assistant shortens and rephrases inside the grid. It is the editor we recommend.
Switching takes one click. A button in the editor header reads Try editor v2, and To editor v1 brings you back. Your filters, columns and current segment travel with you both ways. Nothing changes until you use the switch, and your choice is yours alone, so your account default and your colleagues are unaffected. The Editor v2 interface is in English for now.
The old home-page panel that moved users between the classic editor and Editor v1 is removed, along with the account-wide dropdown inside it; administrators keep the access right Use multicolumn editor by default for that. Links opening the editor from a word count report or an offline package now take each user to their actual version, and users working in the classic editor are not moved.
Editor, Translators - WM-27438
New New Workflow Rule Requiring All Editable Segments to Be Confirmed Before a Job Can Be Completed
A new optional workflow setting, "Jobs can only be completed when all editable segments are confirmed with green status", prevents a linguist from marking a job complete while any segment they can edit is still red, gray or untranslated. It sits next to the existing error-free-QA option in the Workflow & Suppliers step settings, is off by default on all existing and new workflows, and applies to both Standard and Codyt jobs. Locked or read-only segments are never counted, so a linguist is never blocked by content they cannot change, and a segment that has a translation but was never confirmed still counts as not done. When completion is blocked, the message states how many segments still need confirming, and in the Editor the "All editable segments confirmed" checklist row shows the count with an Apply filter button that jumps straight to them. Users with the Administrator profile are exempt from this rule and, from this release, also from the existing "Jobs can only be completed after an error-free QA check" rule: on projects already using that option, an administrator can now complete a job even when the QA check still reports errors. Project managers without the Administrator profile remain subject to both rules. For more information, see: https://help.wordbee.com/wbt/workflow-template-automation-options and https://help.wordbee.com/wbt/job-acceptance-and-delivery
Wordbee Website, Project Managers, Administrators - WM-26952
New Live Word Preview in Editor v2
Translate a Word document and watch the page form as you type. A panel below the grid shows it exactly as it will be delivered, colors, images and layout included, redrawing on every keystroke. Move or detach the panel, click any paragraph to jump to its segment, switch between source and target, and see what is still untranslated.
Live preview covers Word .docx documents, and you can download the preview from the panel. Other formats keep the existing preview.
It is in Editor v2 only. Open the editor, click Try editor v2 in the header, and see it on your next Word document.
Editor, Translators, Project Managers - WM-26880
Improved View Job Status History Directly From the Job Lists
The job status shown in the job lists is now clickable and opens the status history popup, the same one already available on the job details page, so you can see when a job changed status and who changed it without opening each job. This works on four screens: Jobs > Standard jobs, Project details > Jobs, Jobs > Codyt jobs, and the Codyt project's 5. Jobs (Manage items) tab. On Codyt lists, only the status half of the Current work cell is clickable, and the popup shows the history of that specific workflow task, titled with the task name. A row is clickable whenever a workflow task exists behind it, including tasks showing Not assigned, while document rows with no workflow task yet stay inert. Suppliers see the same clickable status on their own jobs, and worker names remain hidden from users who lack the corresponding right. For more information, see: https://help.wordbee.com/wbt/managing-standard-jobs and https://help.wordbee.com/wbt/managing-codyt-jobs
Jobs, Translators, Project Managers - WM-27389
Improved Pricelist Choice Restricted to the Supplier's Configured Pricelist on Outsourced Projects
When you edit an outsourced project whose supplier has a Default client pricelist configured, the pricelist dropdown now offers only that pricelist instead of every pricelist available to the project's client. This removes a real repricing risk: previously anyone editing the project could save a different rate card by accident and quietly change what the client is billed. If the project already holds a different pricelist, that current value is kept and offered as the only second choice, so saving the page never changes anything on its own and aligning a project is always a deliberate act. Nothing changes when the supplier has no configured pricelist, or when that pricelist is not shared with the project's client; in both cases the full list is still offered, and the form explains why. Projects that are not outsourced are unaffected.
Wordbee Website, Administrators - WM-26961
Improved Edit Effort Now Measured per Job Instead of per Assigned Person
A job's edit-effort figure now counts exactly the editing done inside that job, whoever did it and however the job was allocated. Until now the figure was reconstructed by matching edits to the person the job was assigned to, so a job outsourced to a supplier company showed a blank, a job two people worked on counted only one of them, and two jobs on the same document could not be told apart. Every segment save now records which job it was made under, so jobs allocated to a supplier company or to an AI agent supplier produce a percentage, reassigned jobs count everyone's work, and repeat jobs separate naturally. Edits through every write path are counted, including all editor versions and Excel, Word and XLIFF import inside a job, while text written outside any job such as machine translation and pre-translation is not counted as editing. This works forward only: a job created before this release carries no job reference and stays blank permanently. For more information, see: https://help.wordbee.com/wbt/job-edit-distance
Jobs, Translators - WM-27415
Fix Suppliers Can No Longer Decline a Finished Job
Suppliers can no longer hand a job back once it is finished: the decline option is no longer offered on a Completed Codyt job, nor on a Standard job that is Completed, Approved or Closed. Previously it stayed available at every status, and using it emptied the job and reset it to Draft even after the work had been delivered and invoiced. The restriction applies in the Jobs menu and in the editor, and is enforced when the action is submitted rather than only hidden on screen. Project managers are now always told when a supplier declines: on Standard jobs the notification goes out whether or not the supplier typed a reason, and on Codyt jobs the supplier's explanation travels with it. Declining before completion is unchanged and remains a normal supplier action.
Wordbee Website, Project Managers - WM-26949
Fix Corrected Values and Two New Columns in the S411 and S721 Oversight Reports
In report S411 (Jobs - Status & Suppliers), the "Last approved" column now shows when a job's results were actually approved, matching the job's status history, instead of the time the job was completed; it is blank for jobs that were never approved and for Codyt jobs. S411 also gains a "Job Total Time Spent" column showing how long each job took from work start to completion, formatted as dd hh:mm so it sorts and filters in Excel. In report S721 (File QA Oversight Per Language), the "Job types" column now shows the task categories involved rather than repeating the value already in "Project type", and a new "Order ID" column lists the order numbers the project originated from. Both new columns are added at the far right of their sheets, so existing column positions are unchanged, and all four values are recalculated each time a report runs. Customers using a customized copy of S411 or S721 receive the corrected values automatically, but will only see the two new columns after re-uploading their template. For more information, see: https://help.wordbee.com/wbt/report-s411-jobs-status-suppliers and https://help.wordbee.com/wbt/report-s721-file-qa-oversight-per-language
Reports, Project Managers - WM-27410
Fix QA Spelling Rule No Longer Uses a Disabled Dictionary
The Spelling rule in a QA profile now respects the enabled state of a spellcheck dictionary. When an administrator disables a dictionary on the Spellcheck dictionaries page, that page and the help documentation both say the setting controls whether the dictionary is available to the editor and to the QA tool. The editor honored it, but QA did not: it picked its dictionary by matching the target language only and never looked at the enabled state, so a dictionary an administrator had deliberately disabled kept flagging words in QA reports. Where a language has no enabled dictionary left, the Spelling rule now reports nothing for that language instead of producing issues from a dictionary nobody wanted. Choosing a specific dictionary on the rule is unchanged. For more information, see: https://help.wordbee.com/wbt/qa-categories
QA, Translators, Project Managers - WM-27372
Fix Deliveries, Exports and Previews No Longer Fail on a Stray Formatting Character
A single stray formatting character inside a stored translation could make a whole operation fail with a technical error and produce nothing, blocking deliveries with no way for a project manager to fix it. Finalizing documents, segment export, offline export, MT Hive translation and document preview now always complete: the affected text is written out as plain text, and every other segment is unchanged.
Parsers, Project Managers - WM-27428
Fix Word Documents From Generating Tools Keep Their Line Breaks
Line breaks (Shift+Enter) in Word files produced by generating tools rather than by Word itself were being dropped, so sentences arrived joined together in the delivered translation. They are now picked up and shown in the editor, and restored in the translated file. Affected documents must be re-uploaded to benefit, which changes segment boundaries.
Microsoft Word, Translators, Project Managers - WM-27454
Fix Excel Targets Preserve Formatting Across Text Directions
Excel files translated between left-to-right and right-to-left languages now open without requiring repair. Regenerated target files preserve cell formatting, comments, and the correct target-language alignment.
Parsers, Project Managers - WM-27446
Monday, September 7, 2026 - Version 2026.3.10.0 Azure-EU Switzerland
New New QA Rules for CamelCase, Uppercase Words, URLs, Emails, and Codes
Four new built-in QA rules catch technical tokens that were changed by accident during translation: camelCase terms such as getUserName, fully uppercase words such as MAX_RETRIES, web addresses and email addresses, and alphanumeric codes such as AB123X4. Each rule compares source and target in both directions, so a token that was altered, dropped, or added is flagged with a precise message during the regular QA pass. You can enable and configure the rules per QA profile, including a minimum token length for the uppercase check, and the results appear in the QA panel. All four are disabled by default, so existing QA profiles keep working exactly as they do today until an administrator turns them on. For more information, see: https://help.wordbee.com/wbt/qa-categories
Wordbee Website, Translators, Project Managers, Administrators - WM-26730
New Filter and Search the Webhook Calls Activity Log
The Webhook Calls page under Settings, then Activity, now has filters, so you can find specific calls without paging through the whole list: search by URL, filter by outcome (Success or Failed), and narrow to a creation-date range. The filters work the same way as on other list screens such as Find jobs and User operations, and they are remembered when you leave the page and come back. Any successful response, such as 201 or 204 and not only 200, now shows as a success rather than a warning. The page also states that webhook calls are kept for 7 days before being deleted automatically. For more information, see: https://help.wordbee.com/wbt/system-activity
Wordbee Website, Administrators - WM-26824
New Reusable Job Checklists for Workflow Steps
You can now build reusable job checklists in Settings, under Project and work processes. A checklist holds a name, an internal note that suppliers never see, and a list of requirements such as "Glossary applied" or "Client style guide followed", with each item marked optional or mandatory. Attach a checklist to a step in a workflow template or to a step on a project's own workflow, and every job created on that step carries the same requirements. When you edit a checklist, the jobs that use it pick up the change, so nobody retypes instructions job by job. This applies to both Standard and Codyt projects.
sql, Workflows, Project Managers - WM-26787
New Job Edit Distance Available in the Jobs List API
The Jobs list API can now return the edit-distance figures Wordbee already records for finished jobs: how much the translator changed the text, and how far the final translation ended up from the raw machine translation it started from. Four new columns are available on request and use the same names and meanings as the matching report columns, so what you pull through the API matches what the report shows. Jobs with no stored figures return empty values, and nothing changes for calls that do not ask for the new columns. For more information, see: https://help.wordbee.com/api2/jobs-list
API, Translators - WM-26978
Improved Confirmation Step Before Setting a Project to Completed, Archived, or Cancelled
Changing a project's status to Completed, Archived, or Cancelled now asks you to confirm before the change is applied. Each message names what that status can set in motion, such as client notifications, automatic archival, or the cancellation of open jobs and quotes, so a single mis-click no longer triggers something you cannot undo. Declining leaves the popup exactly as it was, comment text included, and all other statuses still apply on the first click. This applies to both Standard and Codyt projects. For more information, see: https://help.wordbee.com/wbt/become-the-manager-and-update-the-status-of-a-translation-project
Wordbee Website, Project Managers, Administrators - WM-26967
Improved Show the Previous Job Deadline to Suppliers at Proposal Status
In Standard projects with multi-step workflows, a supplier looking at a proposal for a dependent job, such as a review job that follows a translation job, could only see the preceding job's deadline after accepting the proposal. The Standard job details page now shows it while the job is still at Proposal status: a note explains that the job depends on preceding jobs that are not yet complete, and the "Previous job deadline" line gives the date the predecessor is expected to finish. Suppliers can decide whether to accept without the project manager sending the timing separately. This covers allocated proposals, group job openings, and crowd jobs, and other job statuses behave as before. For more information, see: https://help.wordbee.com/wbt/accept-decline-standard-jobs
Wordbee Website, Administrators - WM-26969
Improved Supplier Group Creation Offers Only Enabled Job Types
The Job type list on the new supplier group form used to include every job type ever configured for the company, including ones that had since been switched off, so a group could be tied to a job type that can never receive work. The list now shows only the job types the company currently has enabled, and the preselected default is always an enabled one. If a job type is switched off while the form is open, saving the group is refused instead of creating an invalid group. Existing supplier groups are unaffected, and the job type filter on the groups list still offers the full list.
Suppliers, Project Managers, Administrators - WM-26962
Improved Image to Text OCR Moved to Microsoft's Supported Vision Service
Microsoft is switching off the version of its vision service that the Image to Text (OCR) feature called, on 13 September 2026. Without this change, OCR would stop working on that date for every platform configured with Microsoft OCR. Wordbee now calls Microsoft's supported service instead, reusing your existing settings and key, so nothing needs to be reconfigured and the same actions work as before. Language coverage improves substantially: printed text goes from 25 to 164 languages, and handwriting from English only to nine languages. Two things may differ: the text extracted from an image can come out slightly different, usually better, and images smaller than 50 pixels are no longer accepted because Microsoft's new service will not read them. Both Microsoft entries, Printed Text and Handwritten Text, stay in the OCR system choices, and they now give the same result because the new engine detects handwriting on its own.
Wordbee Website, Translators, Project Managers - WM-27095
Improved Supplier Messages Stay Private in Group-Proposal Jobs
In a Standard job opening offered to several suppliers at once, where the first to accept gets the job, each invited supplier now sees only their own company's messages and the project manager's, never a message written by a competing supplier. A competitor's message could previously appear in the messages dialog, in the "Last message" preview, and in the job tooltips on the Find jobs and project Jobs lists before the job was assigned. Standard jobs now match the confidentiality that Codyt jobs already provide. The message history opened from Find jobs also works correctly and shows a supplier their own messages and the manager's. Allocated jobs, crowd jobs, where sharing is intentional, and Codyt jobs are unchanged.
Wordbee Website, Administrators - WM-26951
Improved Style Rules Support for the DeepL Machine Translation Connector
The DeepL machine translation connector now supports DeepL Style Rules. In the connector settings, an administrator can load the style rules available in the DeepL account and pick one rule per target language, next to the existing Glossaries option. Translations into a language with a selected rule apply it automatically, so machine translation output follows your organization's writing-style preferences. Style rules are created and managed in your DeepL account and require a DeepL Pro API subscription. DeepL currently offers them for eight target languages: German, English, Spanish, French, Italian, Japanese, Korean, and Chinese. A connector with no rule selected behaves exactly as before. For more information, see: https://help.wordbee.com/wbt/deepl
MT, wbt, Project Managers, Administrators - WM-26465
Fix Improved Pricing Cache Stability on Shared Servers
An account with a very large number of price lists could overload a shared server cache and slow down or interrupt service for everyone working on that server. Pricing data for such accounts is now stored more efficiently, and the system rebuilds its pricing cache far more quickly when it needs to. Nothing changes on any screen or in any workflow, and the first price-list load is now faster for every account.
Core, Project Managers, Administrators - WM-26979
Fix Order Cancellations No Longer Reveal an In-House Client's Contact Details to Suppliers
When an in-house client cancelled an order, Wordbee cancelled the linked project and its jobs automatically. It also recorded the client as the person who cancelled each job and sent the supplier's job-cancellation email from the client's own name and address, so translators could reply to the client directly. Those automatic job history entries and cancellation emails now come from the project manager. When a project has no manager, the job history shows the admin and the email comes from the agency's own company mailbox. The client's name still appears on the order cancellation they performed themselves, and internal audit records are unchanged.
Wordbee Website, Administrators - WM-26968
Fix MT Badge and Engine Name Now Visible to Every User
On a machine-translated segment, the MT badge and the name of the engine that produced the translation are now shown to every user. External translators and reviewers previously saw neither in the Editor, and no engine name, because a single access restriction in shared code withheld it. Knowing which engine produced a translation helps a post-editor judge how much to trust it.
Editor, Translators - WM-27122
Fix Reliable AI Hand-Off When a Job Starts Automatically
When a job assigned to an AI agent started on its own, for example because the previous job in the workflow was completed, the AI work could fail to start without saying so: the job showed In progress with no AI run recorded against it. The hand-off now works reliably, and if one does fail, the job history records a line saying so, so the problem is visible instead of silent.
AI, Project Managers - WM-27078
Fix AI Runs No Longer Fail on Segments Containing Quoted Phrases
AI post-editing, translation, and quality runs failed on files where a sentence contained a quoted phrase, such as a quotation followed by a comma. Those files now complete with the quotation marks preserved, and files that already worked are unchanged.
AI, Project Managers - WM-26837