Each account has limits on size and on the number of analyses, and each report stays available for a period. The numbers on this page are the console defaults; the Analyses page shows the values for your account right below the Upload and analyze button.
Upload and analysis limits
| Limit | Default | How it works |
|---|---|---|
| Size per upload | 4 GiB | Total size of the files in one upload, as they arrive, compressed or not. |
| Content after decompression | 25 GiB | Applies to each uploaded file: the decompressed trace, the total of the files in a zip or tar, or the assembled trace of a collection. |
| Compression ratio | 1,000 times | A file that grows more than that when decompressed, after the first 10 MiB, is rejected for safety. |
| Files in a zip or tar | 20,000 | Above that, the package analysis ends with an error. |
| Files in a collection | 20,000 | Above that, the upload is refused. |
| Files per upload | No limit | Each file becomes an analysis, and they all have to fit in the queue and in the stored analyses. |
| Queued analyses | 20 | Analyses queued or processing at the same time. |
| Stored analyses | 200 | All analyses in the account, including those with errors, until the period expires or you delete them. |
| Concurrent uploads | 1 | One upload per account, counting browser, app and API. |
| Processing time | 60 minutes | Past that, the analysis ends with an error. |
| Upload chunk | 8 MiB | The page, the app and the API send the file in chunks of up to that size, one at a time. |
The console administrator can set different limits for your account. The size per upload never exceeds the server ceiling of 4 GiB. If the upload stops midway, what has arrived is kept for up to 24 hours without a new chunk; on the page, only while your browser session lasts.
Report retention period
- The report stays available for 7 days by default. The console administrator sets the period, from 1 to 365 days, and the Analyses page shows the one in effect, as in Each report is available for 7 days.
- The period counts from the upload of each file. Once it expires, the analysis is deleted in the next cleanup, within 10 minutes.
- Before the end, download the report with Download HTML or Download JSON. You can delete the analysis before the period ends, whenever you want.
- The uploaded trace does not wait for the period: it leaves the server as soon as the analysis finishes (retention and privacy).
Repeated upload
WaitScope recognizes the file by the SHA-256 of its content, and only among the analyses of your account: an analysis from another account is never reused.
| Case | What happens |
|---|---|
| The same file, already analyzed | No new analysis is created. The console opens the existing report, with This file was already analyzed on and the date. With several files, the page says how many had already been analyzed; the app says the report is the existing one. |
| The same file, with the previous analysis in error | A new analysis is created: the analysis with an error does not count. |
| The same trace with different compression | The .trc and then the .trc.gz of the same trace, for example: the second upload creates a new analysis. When it finishes, the previous one with the same trace text is deleted, and only the newest remains. |
| Zip or tar with files already analyzed | Those files are left out. If all were already analyzed, the package analysis ends with all traces in zip have already been analyzed; the reports are in the list. |
| The same files to analyze together | In any order, they open the collection that already exists. Uploaded separately, they become the analyses of each file. |
A repeated upload does not renew the retention period, which still counts from the first upload. To keep the report longer, download the HTML or the JSON. To analyze again, delete the analysis and upload the file again.
Limit messages
| Message | When it appears | What to do |
|---|---|---|
| File too large | The upload exceeds the size limit. | Compress with gz, bz2 or zip, or split into smaller uploads. |
| Queue full | The account already has the maximum number of queued analyses. | Wait for some to finish. |
| Analysis limit | The account already has the maximum number of stored analyses. | Delete old analyses, including those with errors. |
| Too many analyses | Each file becomes an analysis, and they do not all fit right now. | Upload as a single process, if that is the case, or delete analyses. |
| Too many files | The collection exceeds 20,000 files. | Upload fewer files in the collection. |
| Upload in progress | Another upload from the account has not finished yet. | Wait for it to finish. If it is in another browser or in the app, ending the other sessions in My account cancels the upload. |
| No space on the server | The server has no space to receive files. | Try again later and let the console administrator know. |
Where to go next
- For what goes into an upload: compressed files and folders.
- To combine the files of one operation: analyze together.
- For what WaitScope keeps and deletes: retention and privacy.