Cloud Release - June 2026
DF-NET480-2026.6.0.2; DocBatch-2026.6.0.2;
Features
![]() | Batch API: Improved Job Cancellation and Processing Reliability | Comprehensive improvements to job lifecycle management, record processing reliability, and error visibility across the Batch engine. Improvements include:
|
![]() | Batch API: Elastic Worker Scaling | The Batch engine now automatically scales document-generation capacity up and down in response to real-time demand — reducing latency during high-load periods and lowering resource use when demand is low. New capabilities include:
|
![]() | Batch API: Polled Generation Enhancements | Improvements to polling-based document generation workflows in the Batch engine. Improvements include:
|
Fixes
![]() | Platform: Fixed error when previewing data from Dynamics on Premises | Resolved an error that occurred when attempting to preview data from a Microsoft Dynamics on Premises data connection in the DocFusion Designer. |
![]() | Platform: Fixed FIPS compliance issue in DocFusion Plugin | Resolved a Federal Information Processing Standards (FIPS) compliance issue in the DocFusion Plugin that prevented it from loading in FIPS-enforced environments. |
![]() | BATCH: Fixed an Error when uploading large multi-record payloads larger than 100MB | Resolved a client-side timeout error that occurred when uploading multi-record payloads larger than 100MB to a batch type configured for record splitting. Uploads now complete successfully regardless of payload size. |
![]() | Batch: Fixed validation bypass after record error correction | Resolved an issue where corrected records in a failed batch would not be re-validated before retrying, which could cause the batch to remain stuck in an error state. |
![]() | Batch: Improved error visibility for record-level processing failures | Fixed an issue where individual record errors (validation and processing failures) were not surfaced in the overall batch status, making it harder to identify and remediate failed records. |
![]() | Batch: Fixed batch type deletion failing when other batch types have active batches | Resolved an issue where deleting a batch type with no associated batches would incorrectly fail if any other batch type in the account had active or in-progress batches. Batch type deletion now correctly checks only the targeted batch type, and includes a performance improvement for this validation check. |

