Cloud Release - June/July 2025
DocBatch-2025.5.0.82; AIS-Logging-2025.6.0.1;
Enhancements
![]() | BATCH: Improved control over scaling engine for Tenants with dedicated resources. | For DocFusion Batch Customer who have enterprise plans with dedicated infrastructure we now provide additional control over how many Validation Tasks and Processing Tasks can be handled concurrently. This allows for better control when tweaking performance for certain workloads. |
![]() | BATCH: Auditing on Batch events | We have added new properties on GetBatch and SearchBatches APIs that now provide timestamps for key events including status changes. |
![]() | BATCH: Removed BatchType data from GetBatch and SearchBatches APIs | IMPORTANT NOTICE: Possible breaking change! The BatchType.Configuration property returned by the GetBatch and SearchBatches API methods now return a null value. This change was implemented to greatly reduce the payload inflation caused by large BatchType configurations. The BatchType ID and Name is still returned and can be used to retrieve the BatchType Configuration independently via the GetBatchType API method. |
![]() | BATCH: Enhancements to Processing Engine | We have introduced various fixes and optimizations that improve stability and robustness when generating large batches. |
![]() | BATCH: Improved performance when bulk deleting batches | We improved the way the Batch Engine handles cleanup of Batches when Deleting or Purging multiple batches at the same time. |
![]() | BATCH: Max Page Size on Batch APIs | We have implemented a maximum page size for the following Batch API methods: SearchBatches: 10 000 SearchBatchRecords: 20 000 |
![]() | BATCH: Large Payload Splitting and Data Extraction (XML, JSON, CSV, Flat Files) | We have introduced the ability to configure Batch Types with a Data Extractor. Data Extractors allow the splitting and processing of large data payloads so that a single payload can be used to create a single batch. The extractor configuration defines how the input payload is split to create multiple smaller payloads used to create Batch Records. Supported Extractors:
|
Fixes
![]() | BATCH: Improved system stability resulting in batches not getting purged. | We resolved an internal stability issue resulting in batches not getting purged after purge date was reached. |
![]() | BATCH: Fixed and issue with incorrect response on authentication failures. | Resolved an issue where authentication failures would not return 401 response as expected but returned 200 response with HTML response body. |
![]() | BATCH: Improved event handling after batch approval | We have resolved an issue where a delay is introduces between approval of a batch and when processing starts. Processing now starts immediately upon approval. |
![]() | BATCH: Fixed an issue with batch counts lagging behind due to state event queue oversaturation | We resolved an issue where oversaturated event queues resulted in delays while keeping batch counts up to date. The end result is that processing starts and continues at a consistent rate but the reported number of processed items were incorrect at a specific point in time until oversaturation of the event queues were resolved at which point the processed counts would catch up to the actual value resulting in a sudden perceived spike in processing rate. The affected GetBatch and SearchBatches API methods in scenarios where the processed count was used for real time tracking of progress or processing rate. |
![]() | BATCH: Improved batch processing performance and stability under peak load scenarios | We have enhanced batch processing performance with improved system reliability. This update enhanced our backend infrastructure to handle large data volumes more efficiently, resulting in:
|
![]() | BATCH: Fixed an issue when deleting batches in "Completed with Errors" state" | We resolved an issue where deleting batches in "Completed with Errors" state would result in an error "Batch must be cancelled or complete to delete" |
