The short version: the limit is 30 files in flight at once, not 30 per session. As uploads finish, their slots free up — so you can keep adding to the same window until everything is in, without closing and reopening it.
What happens when you select more than 30
Nothing is lost and nothing fails. DocuBuild adds as many as fit and shows you a line like:
| — | “Up to 30 files can be uploaded at once — 30 of the 47 selected files were added. Please upload the rest in another batch.” |
The 17 that didn't fit were simply not added. Once the first batch has gone through, drag the remainder in — they start uploading straight away.
You don't have to wait for the whole batch. Completed files release their slots as they go, so on a slow connection you can keep topping the window up rather than sitting through 30 files before starting the next lot.
Reading the upload list
Each file gets its own row, and the row shows you where it is rather than labelling it in words. What you'll see, in order:
| What the row shows | What's happening | What you can do |
|---|---|---|
| Listed, no progress yet | Waiting its turn — files go up one at a time. | Remove it if you added it by mistake. |
| A moving progress bar | Transferring now. | Cancel stops just this file. |
| Bar full, still working | Transferred; DocuBuild is filing it. | Let it finish — it's nearly done, and cancelling is no longer offered. |
| An error, with Retry | The transfer didn't complete. | Retry that one row. |
| A tick | Done and filed. The document exists in the project. | Nothing — and completed rows stay put. |
A failed row doesn't hold up the others. The rest of the batch keeps going, and you can retry the failure on its own without re-selecting anything.
Interruptions
DocuBuild retries by itself, backing off a little further each time. A brief dropout on site usually recovers with no action from you — the row keeps its progress rather than starting over.
Uploads are resumable. Come back, add the same file again, and the transfer picks up from the bytes already sent rather than starting from zero. This matters most for large drawings and models, where restarting would mean re-sending gigabytes.
That's the file-type check, and it runs before any data is sent — so it costs you nothing but a moment. See which file types can I upload for the accepted list and what to do about a format that isn't on it.
Notifications for a batch
A batch does not email one notification per file. DocuBuild waits until the batch has finished and sends a single message covering everything that landed — so uploading 30 documents against a condition notifies the reviewer once, not thirty times.
Let a batch finish before closing the window. Because the notification is sent at the end, closing part-way can leave the documents uploaded but the notification unsent. The files are safe and visible in the project — but the person waiting on them may not hear about it. If in doubt, tell them directly, or upload the stragglers as a fresh batch.
Uploading whole folders
DocuBuild takes files, not folder trees. Dragging a folder in won't work — open it and select the files inside. Where a folder structure genuinely matters, ZIP it and upload the archive as a single document, or ask us about a bulk import.