A document failed to process
A document can fail for reasons Merchaint cannot fix on its own: a scan too faint to read, a password-protected PDF, a file that is not really a document at all.
- A walkthrough video, then how to clear the queue
- Why reading the message beats retrying blindly
- The failures that arrive with no message
- Why the same failure appears twice, under different buttons
01 · Video
Feature walkthrough
02 · Why
Why is there a queue at all?
A document can fail for reasons Merchaint cannot fix on its own: a scan too faint to read, a password-protected PDF, a file that is not really a document at all.
Rather than silently dropping them, Merchaint puts them in one place with a reason.
03 · How
Clear a failure
- Go to Documents → Exceptions.
- Read the ERROR TYPE and the message under the file name.
- Tick the ones you want to deal with.
- Press
Retry Selectedto try again, orDismiss Selectedto clear them away.
04 · Expected result
A retried document goes back through processing and, if it works, leaves the queue and appears in the Inbox. A dismissed one leaves the queue without being processed.
05 · Troubleshooting
“Some pages could not be read — reprocess to retry”
The most common one. Usually a scan quality problem. Retry once; if it fails again, the file itself needs replacing with a better copy.
The RETRIES column says 3 and it is still here
It has already been tried automatically. More retries will not help — get a better copy of the document.
06 · Notes
A banner sometimes says “Reconnecting to real-time updates…”
It appears at the top of the page and means the live connection dropped and the page will catch up on its own. Refresh if it stays.
07 · FAQ
Common questions
It takes it out of the queue. It does not un-receive it.
Not really — the queue is what happens when reading fails. Better quality documents mean fewer.
A clear scan where you could read the numbers yourself without squinting.