Docling has shipped version 2.99.0, a minor but meaningful update that brings two key improvements: a new configuration option for S3 operations and significantly better error handling. These changes might seem small on paper, but they matter for anyone relying on Docling for large-scale document processing.
The update introduces S3Coordinates.max_num_elements, a parameter that lets users cap the number of elements retrieved when working with S3 buckets. This is a direct response to performance bottlenecks in large directories. Alongside this, the failure mode handling got a complete overhaul. Instead of cryptic errors, Docling now outputs user-interpretable messages when something goes wrong.
These are the only two changes in this release, but both address real pain points. The S3 limit prevents runaway requests that can slow down or crash pipelines. The error improvements mean operators can actually understand why a job failed without diving into logs blind.
Document processing at scale is unforgiving. A single misconfigured S3 query can stall an entire workflow. With the new parameter, teams can set a hard cap and avoid those scenarios. The error handling upgrade is equally critical. In production, unreadable error messages waste hours of debugging time. Now, when a failure occurs, the system explains what happened in plain terms.
This is the kind of polish that separates a hobby project from an enterprise tool. Docling is clearly paying attention to operational realities. It's not flashy, but it's exactly what users need to trust the system with their data.
Official Source: https://github.com/docling-project/docling/releases/tag/v2.99.0