The short version: R5 lets you run multi-threaded file processing at full throughput in production, and gives the large project and task grids a stable, reproducible sort order. For teams working hundreds of files at once, that is the difference between a queue that behaves predictably and one you have to double-check by hand.
This is the fifth release of the 2026 cycle: 3 new features, 5 updates to the processing Agent, 3 improvements, and 10 bug fixes. Here are the three that matter most for regulated teams, and what each one changes.
Multi-threaded processing runs at full throughput, and errors now identify the file and the reason
Pillar: atomic extraction.
Before a file can be reviewed in Aproove it has to be broken down: ripped, rendered, sliced into the components a reviewer sees. Multi-threaded processing makes that fast, and until R5 it was not safe to leave on. On real production files it could crash or deadlock, and the project would sit in Processing indefinitely, stuck at zero or stalling around seventy percent, with no usable error reaching the user. It now completes reliably, so the full throughput is available in production.
Diagnostics changed alongside it. When a PDF cannot be rasterized, the error identifies the file that failed and the reason it failed, rather than leaving the project sitting in a generic processing error. Previously the log held nothing useful, and the release note is blunt about what finding the culprit in a large upload took: re-uploading batches of placeholder files until the project moved, which could take hours on a big job. The message is also written to the specific failure rather than to one catch-all cause. A password- or certificate-protected PDF is now named as exactly that, where the previous wording pointed at a single unrelated cause and left protection to be guessed at, so a protected file was indistinguishable from a genuinely damaged one. Animated GIFs with an odd pixel width or height, which produced no output at all while even-dimension GIFs in the same project processed normally, now process correctly.
When marketing, compliance and legal are all waiting on the same batch, a stalled project is not a technical inconvenience. It is three teams idle against a deadline, with nobody able to say which file caused it.
The Projects and Tasks grids now sort deterministically
Pillar: decision-based workflows.
Rows that share a value, the same status, the same deadline, the same metadata value, now keep a stable and reproducible order instead of being reshuffled between pages and between reloads. Previously, scrolling a few hundred entries could show you the same record twice or skip one entirely, because the underlying order was not guaranteed when values tied.
That is a review completeness problem before it is a usability one. If your work queue is four hundred variants and the list quietly drops one as you page through it, the item does not get flagged as missed. It simply never appears.
Three related changes ship with it. Projects with no value in a sorted metadata column now sort last rather than first. Metadata columns in the Tasks grid can be sorted at all, which they could not before. Metadata columns that merge several teams are now consistently non-sortable, instead of silently sorting on one team's values at random. Columns in the Assets Dashboard are sortable too, which brings it in line with the other grids in the product.
Forms get a true single-choice field
Pillar: built-in auditability.
Form metadata is not merely decoration in Aproove. It drives routing, and it becomes part of the record of how a project was handled. R5 adds a Radio Button Group metadata type: two or more options, laid out vertically or horizontally, with required-answer validation and full compatibility with existing conditional logic.
Also in this release
- Page offsets now advance based on the page count of the file just added, so a document longer than the offset no longer overlaps the pages of the one before it.
- Time tracking becomes an area of the product in its own right rather than a scattering of fields, with a timesheet menu in the Admin and a timesheet tab on project tasks.
- Microsoft 365 document editing is a soft launch. The configuration is present in the Admin to review and prepare, final approval from Microsoft is still pending, the integration is not yet live, and no existing installation changes behavior.
- "Commit actions immediately" is enabled by default on newly created task decisions, which matches how the option is set in the large majority of workflows audited internally and at customers. Existing decisions are untouched and the checkbox stays editable.
- Ten bug fixes are included, among them HTML (Local) projects generating proofs consistently, collection exports surviving project names with accented characters, and imported workflows rendering their connector lines where they belong.
What this means for regulated teams
Take a print provider running pharmaceutical inserts and carton artwork. A single submission is a few hundred press-ready PDFs, high resolution and CMYK, and each one carries mandated language that has to match the approved copy exactly. Marketing owns the artwork, compliance checks the regulated content, and legal signs before plates are cut.
Three R5 changes apply to that work directly. Multi-threaded processing means the batch renders at full throughput instead of being run conservatively to avoid a stall, so the review window opens when it was planned to open. When one file does fail, the error names it and says why, and a corrected file goes back in while the rest of the batch carries on, rather than the whole submission waiting on a hunt. And when a reviewer opens a task list of four hundred items and sorts it by status, that list is the same list on page one and on page eight, which is what turns "we reviewed every item" into a claim rather than an assumption.
FAQ
Do I need to change anything to get the agent enhancements and multi-threaded processing fix?
No. The processing Agent is updated alongside the release update, so the fix arrives with the upgrade rather than needing anything switched on.
Up next
R6 completes the Microsoft 365 switchover, including moving an installation across in a single step and aligning the naming in the Projects tab.
