Open Legal Products tightens the upload pipeline, but leaves it on the review bench
A closed, unmerged proposal would make large document uploads more dependable, safer to process, and clearer for users.
The proposed follow-up addresses the unglamorous failures that can derail a legal team's first interaction with a matter workspace: uploads rejected by storage providers, sessions expiring mid-batch, stalled conversions, and a screen that reports every file failed when only one has a problem.
- Uploads would be bound to the expected file size and type, preventing a signed upload link being used for something else.
- Large selections would be split into manageable batches rather than rejected outright.
- Each file would retain its own recorded outcome, so completed documents stay visible when another file stalls or fails.
- Processing work would recover from timeouts and queue contention instead of quietly tying up capacity.
The branch also fixes deployment ordering that could otherwise leave the upload feature unavailable. None of this has landed, so it is a useful signal of the maintainers' direction rather than current product behaviour.
So what Legal teams planning high-volume intake should watch this work because reliable per-file handling is what turns bulk upload from a gamble into an operational workflow.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?