Uploading
Drag and drop or browse, what Struxen accepts, the batch and size limits that apply on each path, and what every rejection message means
Uploads happen on the Document Center. Start from the drawer the files belong in, so the filing decision travels with them.
Upload files
- Open Documents and click the card for the drawer these files belong in.
- Click Upload in the drawer header. The Drawings drawer says Upload set and opens the drawing-set flow instead; see Drawing sets.
- On the Add documents page, drag files onto the dropzone or click Drop files here or click to browse.
- Check the staged list. Remove anything you did not mean to add.
- Click Upload N files.
The page you came from is named in the breadcrumb and is where a fully successful batch returns you, with the files in it. If any file failed you stay on the upload page, because the failed rows and their reasons are there.
Files go straight from your browser to storage, so a 182 MB drawing set uploads the same way a 2 MB spec does.
A batch started from a drawer is filed under that drawer's category, all of it. The card header says so: Upload to Reports & Investigations, and beneath it "Everything in this batch is filed under Reports & Investigations." A batch started from the generic entry declares nothing, and every file in it lands in Needs filing.
There is no folder upload. The picker takes files, and dropping a folder does not walk it.
What Struxen accepts
Twenty file extensions, and nothing else. The dropzone summarises them as PDF, images, Office docs, text.
| Group | Extensions |
|---|---|
.pdf | |
| Images | .png .jpg .jpeg .gif .tif .tiff .bmp .webp .heic .heif |
| Word | .doc .docx |
| Excel | .xls .xlsx |
| PowerPoint | .ppt .pptx |
| Text | .txt .csv .rtf |
The same list is enforced in the browser and again on the server, so a caller that skips the page gets the same answer.
No CAD or BIM formats. .dwg, .dxf, .rvt, .nwd, .ifc and their
relatives are refused. The ingestion pipeline cannot read them, and accepting
one would produce a document row that never finishes processing. Export a PDF
and upload that.
What each accepted type does after it lands differs a great deal. Office files are accepted and stored; they are not parsed. Images are read by vision only. Read Processing before you decide which file to upload, especially if your PDF is a scan.
The extension test is exact and reads only the last dot. Two names that look
fine are refused: a file called .pdf with no stem, and a name with a trailing
space such as S-111.pdf . Rename the file and try again.
Limits
These are not one global number. Each upload path enforces its own, and they differ.
| Path | Per file | Per batch | Types |
|---|---|---|---|
| Documents upload | 500 MB | 50 files, 3 uploading at once | The 20 extensions above |
| Drawing set upload | No size check | One PDF at a time | .pdf only |
| STRUX chat attachment | 100 MB | One at a time | .pdf .jpg .jpeg .png .tiff .tif |
The 500 MB ceiling on the Documents path exists because the upload is signed once for 30 minutes and there is no way to re-issue it mid-transfer. A file larger than that would too often fail at the very end, after spending your bandwidth, so it is refused up front.
The drawing-set flow checks only that the file is a PDF. A full set of several hundred sheets is expected there.
Lookup tables for every limit in the product are at Limits, and the format list is at File types.
Watching a batch
Each staged file shows its name, its size and a status chip. Every file is tracked on its own, and one failure never stops its siblings.
| Chip | What it means |
|---|---|
| Queued | Staged, not started. |
| Uploading 42% | Bytes are moving. |
| Finalizing | The bytes have landed and the document record is being written. |
| Uploaded | Done. Processing starts now. |
| Failed | This file did not land. The reason is printed under the row. |
Progress deliberately stops at 99% and switches to Finalizing until the document record is written and ingestion is fired. Showing 100% before that would be a lie about what has happened.
When the batch ends, files that landed clear from the list and you get "3 files uploaded. Processing starts now." Files that failed stay on screen with their reason, and the button changes to Retry N files when every remaining row is a previous failure.
There is never a blanket success message over a partial batch. Both halves are reported.
Why a file was refused
| Code | Message you see | What to do |
|---|---|---|
UNSUPPORTED_TYPE | "…is not a file type Struxen can read. Accepted: PDF, images, Office docs, text." | Convert it. For CAD, export a PDF. |
EMPTY_FILE | "…is empty" | The file has no content. Check the source. |
TOO_LARGE | "…is 812 MB, over the 500 MB limit" | Split it, or compress it. A drawing set can go through the set upload instead, which has no size check. |
BATCH_LIMIT | "…was not added. Upload at most 50 files at a time." | Upload in batches of 50. |
DEMO_READ_ONLY | "…was not uploaded. The demo project is read-only." | Switch to a real project. |
NO_PROJECT | "…was not uploaded. Open a project first." | Open a project, then upload. |
UPLOAD_FAILED | The transport's own message | Retry the file. If it keeps failing, check your connection. |
Drag and drop does not honour the file picker's type filter, so a dropped file of the wrong type is refused by name here rather than silently ignored.
Projects that mirror Autodesk Forma
A project whose source is Forma refuses direct uploads with a 409 and this message: "This project mirrors documents from Autodesk Forma. Direct uploads would diverge from the source. To add documents, upload them in Forma; they will sync automatically."
This is a property of the project, not of the file. Nothing you change about the upload will get past it. See Integrations.
Note that the drawing-set upload is not locked on a Forma-linked project. It shows a notice instead, because no Forma path writes into the Drawings register. Drawing sets explains why.
Demo projects
The demo project is read only and the server enforces it. The dropzone stays visible so the flow is still legible, but nothing stages and nothing uploads.
Troubleshooting
The Upload button in a drawer is disabled with a tooltip about categories. That drawer has no category the document API can record, so a file added there would land in Needs filing instead. Upload from a drawer that does, then use Move to….
The file uploaded but nothing appears in the drawer. Ingestion runs after the upload. Look at the processing lane on the Document Center, and at Processing for what the statuses mean.
A PDF uploaded fine but STRUX cannot find anything in it. The upload is not the problem. Almost always the PDF is a scan with no text layer. See Processing.
Upload fails at the very end on a large file. The signed upload window is 30 minutes. On a slow connection a file near the 500 MB ceiling can outrun it. Retry the file, or upload it on a better connection.