Before the Upload: A Preflight Checklist for Multi-Page PDFs in Skavio Agent Tools

Multi-page PDF jobs rarely fail for dramatic reasons. They fail because the request envelope was never checked: the actual file bytes, the page count, the total batch size, the storage allowance, the queue, or the live quote. Skavio Agent Tools is a company-scoped authenticated document, invoice, audio and data processing API with self-service keys, a shared prepaid credit wallet and asynchronous jobs. That makes preflight an operational step, not a formality. A successful upload is not a processed result, and a PDF that looks small by name may still be expensive by page count. This guide sets out the checks to make before submission.

Measure the document, not the filename

Start with two measured facts: actual file bytes and actual page count. A filename ending in .pdf, or a compressed archive label, is not a size check. The published API limits include 100 PDF pages, so confirm in the current documentation how that ceiling applies to the request you are building before treating it as a target. File work is also quoted using the larger of started 25 MB units or started 10 PDF-page units per source, which means bytes and pages both matter commercially. If a source exceeds the applicable ceiling, adjust the batch and re-measure rather than uploading an oversized file and hoping the server will resolve it. The server remains authoritative for malformed, oversized or over-page submissions.

Check the batch envelope, not just one file

A multi-page PDF is usually part of a batch. Relevant published limits include 100 files, 500 MB total upload, 2 GB company source storage, 100 queued company jobs, four active jobs and seven-day retention. These are separate gates. A batch can pass the file-count check and fail the total-byte check; it can fit the upload limit and still collide with current source storage or queue capacity. Add up the actual bytes across the set, count every file and review current storage before submission. Treat seven-day retention as a product window for retrieving results, not as a legal or accounting retention policy. If the batch is large, plan for queued work rather than assuming every file will move at once.

Get the server quote before you trust an estimate

Price the exact sources before committing to the job. File work is quoted using the larger of started 25 MB units or started 10 PDF-page units per source, and the live server quote at submission is authoritative. Use that quote as a business gate: if it falls outside the approved budget, change the batch before spending time on upload and processing. Keep the server quote with the request record so the approved amount can be compared with what is submitted. A quote is not a completed result, and an accepted job is not evidence that extraction, OCR or conversion has finished.

Make the final go/no-go decision after upload

The last preflight check is an operational one. Use a scoped company key and confirm that the request belongs to the intended company workspace. After submission, track asynchronous state rather than assuming that an accepted upload has produced a usable file. If a request returns an error, check the current job state and official error guidance before deciding whether to submit again. Download results through authenticated access and complete the review before the retention window closes. The final gate is a completed job plus an authenticated, reviewed result, not the upload response alone. That discipline keeps a multi-page PDF workflow predictable without pretending that every document will process cleanly.

Open Skavio Agent Tools →