This page shows items released so far this month.
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