Ready signal
Ready to retry
The file type, size, page count, dimensions, naming pattern, and packet manifest match the limits you entered or reviewed.
Workflow product
Portal Preflight
Use Portal Preflight before retrying failed uploads. It helps you inspect format, size, page count, dimensions, archive paths, metadata, filenames, and packet handoff notes before producing a final copy. It is upload preparation, not acceptance, compliance, legal, or security approval.
Start here
Choose the next recovery path
Upload failed Inspect format, size, page count, dimensions, names, and limits before retrying. Prepare a mixed packet Use file, PDF, image, CSV, archive, manifest, and chunking tools in the order the destination requires. Need a safe sample first Practice with owned sample files before using sensitive records.
Preflight result
Ready or needs review
Use these signals as a practical preflight checklist. A ready signal means the file is easier to review before upload; it does not prove the destination will accept it.
Needs review
Needs PDF review
The PDF is encrypted, scanned, oversized, has unusual page sizes, hidden-content signals, attachments, or metadata that should be inspected before upload.
Needs review
Needs image review
The image is the wrong format, too large, incorrectly sized, outside the needed aspect ratio, or still contains metadata/privacy signals.
Needs review
Needs packet review
The ZIP, filename set, CSV headers, duplicate names, chunk size, or manifest details need attention before a handoff.
Task groups
Start with the part of the workflow that is failing
Identify the likely rejection reason
Start with file type, extension, metadata, checksum, file size, supported-format, filename, and packet-manifest checks before changing the file or launching a server job.
Preflight PDF packets
Check size drivers, page count, page size, text-layer and scan signals, password protection, hidden content, attachments, metadata, and compression options before uploading a final PDF copy.
Preflight image uploads
Check dimensions, aspect ratio, safe-area behavior, file-size targets, metadata privacy, format, and compression before uploading images to a strict destination.
Preflight data and archives
Validate CSV structure, product-style headers, archive paths, duplicate names, nested archives, and upload chunk sizes before files are parsed, extracted, or imported by another system.
Build handoff outputs last
Create manifests, provenance notes, filename previews, chunk plans, and ZIP packages only after file type, size, metadata, hidden-content, archive, and naming signals are reviewed.