V43 Release Notes

V43 Release Notes

Versions 43.0.x and 43.1.x are available to SaaS customers only.

43.1.3 (22 Jul 2026)

Versions 43.1.0 — 43.1.2 were not released and are not supported.

Submissions

New

Flow Run Status for submissions — We've added a Flow Run Status column to the Submissions table on the Submissions page ( Submissions > Submissions).

This status aligns with that of the main flow run used to process the submission, categorizing it into one of four mutually exclusive and collectively exhaustive statuses:

It can also be viewed on the Submission Output page and on the Document Output pages for the submission's documents. While it is being processed, each submission passes through stages, which appear in the Stages column (previously Status) of the Submissions table (e.g., Manual Classification, Manual Identification).

In earlier versions, the Stages column appears as Status

For more information, see v43.1 Navigating the Submissions Page and v43.1 Submission Output Page.

Filtering submissions by Flow Run status — A new Flow Run Status filter allows you to identify submissions whose Top-Level Flow run has failed, making it easier to isolate and troubleshoot failed processing. As part of this change, the “ Halted” submission stage (previously status) has been superseded by the “ Failed” Flow Run Status. If you previously filtered for halted submissions by using the submission state, use Flow Run Status = Failed instead.

Clicking the ID of a failed submission opens the Submission Output page, where you can select View Failed Flow Runs to investigate the failure.

Existing submission states continue to represent the current processing stage of the submission. To identify submissions that are actively being processed, combine the submission stage with Flow Run Status = Running.

To learn more, see v43.1 Document Output Page.

Cancelling submissions— If you need to cancel a submission, you can now do so from its Submission Output page or the Submissions page. When you cancel a submission, any flow runs used in its processing are also canceled, along with any Supervision or Quality Assurance (QA) tasks based on the submission's content. You can also provide a cancellation reason of up to 512 characters. More information on canceling submissions can be found in v43.1 Submission Output Page.

Classification

New

Group uncategorized pages by layout or filename — We've added new grouping options to the Uncategorized Pages panel in the Document Classification Task. You can now view uncategorized pages grouped by:

These grouping options make it easier to review, compare, and process related pages during manual classification, reducing Average Handling Time (AHT). To learn more, see 43.1 Document Classification Task.

.png?sv=2026-02-06&spr=https&st=2026-07-27T09%3A11%3A28Z&se=2026-07-27T09%3A44%3A28Z&sr=c&sp=r&sig=9N72RxG4x6b9DLXrgRNbaaZgxtdzOn%2BYaeI783eriV8%3D)

Table Identification

New

Added keyboard shortcuts for switching between tables — We've added new keyboard shortcuts to the Table Identification annotation experience.

.png?sv=2026-02-06&spr=https&st=2026-07-27T09%3A11%3A28Z&se=2026-07-27T09%3A44%3A28Z&sr=c&sp=r&sig=9N72RxG4x6b9DLXrgRNbaaZgxtdzOn%2BYaeI783eriV8%3D)

Layout Editor

Updated

Shared notes across variations in Structured layouts — When a field is shared across multiple variations in a Structured Layout, changes made to its Notes value are automatically propagated to all matching fields. This update ensures that notes remain consistent across shared fields in layout variations. Learn more in Creating Structured Layouts, Layout Editor Tools & Functionality, and Editing a Structured Layout Variation.

Models

Updated

Updated infrastructure requirements for ORCA VLMs —  ORCA VLMs in v43.1 introduce new infrastructure requirements. Machines running ORCA must have the NVIDIA driver 580 or later, and at least 10 GB of available space in the operating system’s /dev/shm directory. Verify that your ORCA infrastructure meets these requirements before upgrading. For more information on ORCA infrastructure requirements, see Infrastructure Requirements.

Training Data Management (TDM)

Updated

Model-action notification messages for VLM Field Extraction — We've updated the notification messages for common model actions in VLM Field Extraction, such as deploying and undeploying models, rejecting candidate models, scheduling and canceling model training, and exporting models.

The following notification messages are displayed when these actions are completed successfully:

To learn more, see VLM Field Extraction Models.

Preventing duplicate tags caused by capitalization differences —  Tags with the same name but different capitalization are now treated as the same entry. For example, “Vendor”, “vendor”, and “VENDOR” are all mapped to the same value (e.g., “VENDOR”). This update helps prevent duplicate tags and maintain consistency across training data tagging. Learn more in TDM for Classification Models, TDM for Identification Models, and TDM for ORCA VLMs.

Improved training data table CSV export— Training data table CSV exports now include status names instead of numeric status codes and provide layout names alongside layout version identifiers. These changes make exported data easier to review, filter, and analyze. We've also updated exports to include only the most relevant columns for each model type, resulting in cleaner and more focused CSV files. See TDM for Classification Models, TDM for Identification Models, and TDM for ORCA VLMs for more information.

Reporting

Updated

Transmissions of the Usage Bundle to Hyperscience — We've made the following updates to the transmissions of Usage Bundles:

Updated tracking of created pages and submissions— Metrics for created pages and submissions are now updated after successful progression through the Submission Bootstrap Block. In previous versions, these metrics were updated when submissions progressed through the Complete Block, preventing visibility into the volume of pages and submissions still being processed. As a result of this change, data in the Usage Bundle's application_usage CSV more accurately reflects processing volumes, regardless of whether submissions are in the Completed state.

Layout-level Classification accuracy metrics in the Usage Bundle — We’ve added layout-level metrics to the classification_accuracy CSV file in the Usage Bundle’s product_analytics folder. These metrics indicate the level of agreement between keyers and the machine in the classification of documents on a per-layout basis. Layout-level metrics are available only for documents processed after upgrading to v43.1.

Submission Processing

Fixed

Rendering of Checkboxes in PDF documents — Fixed an issue where certain checkboxes in processed PDF documents could be displayed as radio buttons after PDF pagination. Checkboxes are now rendered accurately, preserving the original appearance of PDF forms.

API

New

Cancel Submissions endpoint — You can now cancel one or more submissions through the API by using the Cancel Submissions endpoint. Canceling a submission stops any pending processing and updates its flow_run_status to canceled. The submission’s current stage is preserved so you can see where processing was canceled. Any associated manual tasks are also canceled.

Because cancellation is asynchronous, the endpoint returns a 202 Accepted response. You can track the operation by using the returned status URL.