Release 2026.10.29-1

Improved

• Your license now sets which of our system models you can use for each task, as listed in your order form; models you add yourself are never limited. The Models page, step settings and the License page show what your license includes, and testing a system model it does not include is refused.
• OCR engines and voice input follow your license too. The OCR step and the OCR default offer only the engines your license includes, and an OCR step set to another engine stops with a message saying so instead of reading the pages with a different one. The assistant offers the microphone only when your license includes voice input.
• Use your own Azure AI Document Intelligence resource for OCR. Add it on the Models page (kind OCR, Read or Layout) or with da models add --protocol azure_document_intelligence, then choose it as your OCR default or in an OCR step.
• Use your own Azure AI Speech resource or Azure OpenAI transcription deployment for the assistant’s voice input. Add it on the Models page or with da models add --protocol azure_speech, then choose it as the Voice input default.
• Resume failed transactions (Preview): the assistant, and AI agents you connect, can now finish a failed transaction. It reads why the transaction failed and where it can carry on, then, once you agree, runs the failed step again or resumes from a later step, and can assign the review as it does. It needs the Resume failed transactions permission.
• An import is never quietly incomplete. A ZIP archive holding a file that cannot be imported (an unsupported format such as .docx, or an encrypted or empty file) is refused whole, naming each such file and why; an import connector moves it to its failure folder at once. A transaction stops as Failed when one of its files cannot be read in full (a damaged or password-protected PDF, for example), naming each such file, and Resume from the next step carries on with the other files.
• Saving now refuses code that could never run, naming the step or line: a Data Transform script or condition using code that is not allowed (such as .prototype) or a helper that does not exist; a code rule reading a field the schema does not have, with the closest field; and rule, Transform or condition code reading a name it never declares, such as a misspelt variable, with the name it most likely meant. Names that can never find a value are marked as warnings in the editor.
• A failed transaction names the rule or workflow step whose code stopped it, in the API and to the assistant.
• A failed transaction can be assigned to someone who can resume it. A transaction assigned before it reaches a review step its assignee cannot review stays with them and is marked, so a supervisor can reassign it. The assistant can assign transactions before they reach review, as My Work Queue does.
• The Activity Log records every assignment and release, including those made at upload, by Send To and by a review decision, and shows reviewers by name.
• The audit log records every deletion of your data: pages, source files, exports, ground truth, evaluation runs, lookup tables and their records, memory examples and assistant conversations. Deletions made by your retention settings are recorded too, with the system as the actor.
• Integration API keys used through MCP or the assistant can delete projects, import from connectors, submit to Playground, Memory or Evaluation, change Memory and see metrics when the key holds the matching permission.
• Choose which update emails you receive: What’s new, security advisories, and a new weekly digest of release notes. Subscribe from the Support page, by asking the assistant, or on the website.
• Features in Preview carry a Preview badge where you use them, in the app and in the guide, and a deprecated feature shows when it will be removed.
• The API Deprecation Policy page says what counts as the public API, the 180 days’ notice before any part of it is removed, and how you hear about a deprecation. See API Deprecation Policy.

Fixed

• Changing a transaction’s priority while it was still being processed could drop its review details when it reached Human Review at the same moment.
• My Work Queue no longer offers Assign on completed and cancelled transactions, and the assistant no longer assigns or reprioritises them.
• A Data Transform script or If/Switch condition whose own code throws now fails the transaction at once with its own reason instead of being retried; a step set to continue on error still lets the workflow go on.
• The Work Queue API (GET /api/v1/work-queue) shows a claim, assignment, priority change or new transaction straight away, instead of up to 30 seconds later.
• A temporary storage error while subscribing to or unsubscribing from update emails no longer removes other subscribers, and the page asks you to try again.

API

• The subscribe_to_updates MCP tool takes the topic release_notes.
• The source-files upload response lists email attachments that are not in a supported format under excluded_entries.
• Uploading a file that is not a PDF or an image (a .docx or .txt, judged by its content) is refused with 400 unsupported_file_type, naming the file, instead of failing the transaction later. An import connector moves such a file to its failure folder.

Deprecated

• skipped_entries in the source-files upload response, replaced by excluded_entries, which lists the same attachments. It keeps working until at least 2027-04-30.