Every job comes back with a completion report stating exactly what was and wasn't processed, and why — a real accounting, not a blanket "success" regardless of what actually happened.
The failure mode that matters most
The worst outcome from any automated tool isn't an error message — it's a confident, wrong result with no indication anything went sideways. A silently dropped file in a 50-file batch, or a corrupted page skipped without comment, can cost far more than an honest "this one failed."
What actually gets disclosed
The completion report lists what was processed, what wasn't, and the specific reason for anything excluded — malformed file, exceeded size limit, failed a safety check, and so on. In the rare case a job needs manual attention (a stuck batch, an unrecognized file type), an operator may see metadata like a file's name or type to resolve it — never the file's content.
Where this breaks down — said plainly
- A disclosed failure still means you don't have that output. Transparency about what didn't work doesn't substitute for the output itself — you may need to resubmit a corrected file.
- Some failure classes are inherent to the input (a password-protected file, a corrupted scan) and no amount of reprocessing fixes them without a different source file.
Related guides
Where this fits on the site: this is part of how every job runs here, across all services. See Services & Pricing for what's actually sold, or go straight to Choose your job.