amal66 puts a traffic cop on bulk document uploads
Large document batches should now fail more gracefully, without losing the files that made it through.
Across the project assistant, tabular review and add-documents screens, amal66 is replacing the current upload free-for-all with a measured queue: only two files upload at once.
- Successful files remain available even if others fail.
- A dismissible warning names the files that did not upload, so users can retry them manually.
- Dragged-and-dropped unsupported file types are stopped before they reach the service.
The trade-off is deliberate: a large batch may take longer, but it is less likely to overwhelm the upload service or leave staff guessing what happened. There is no automatic retry, avoiding an extra burst of traffic when a service is already under pressure.
So what Legal teams moving matter bundles or review sets should care because a single bad file no longer turns a batch upload into an all-or-nothing mystery.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?