The exceptions queue
Exceptions collects documents Merchaint couldn't read, grouped by what went wrong. It's a short daily list.
- A walkthrough video, then why failures are grouped by cause
- How to open, filter and clear the queue
- What an empty queue does and does not tell you
- Troubleshooting notes, then FAQ
01 · Video
Feature walkthrough
02 · Why
Why do we have this?
A document that failed to read is invisible everywhere else. It made no record, so it will not show up in a module and nothing will match against it. Without one list of failures, the only way to notice is when someone asks where an invoice went.
Failures are grouped by cause because they usually arrive in batches — one bad scanner, one supplier's new template. Grouping turns twenty problems into one fix.
03 · How
- Open
Exceptionsfrom the Documents group in the sidebar. The heading shows how many there are. - Filter by category to group failures by cause, and sort by newest or oldest.
- Open one to see what went wrong.
- Deal with it — fix the cause, then try the document again.
04 · Expected result
A list of failed documents with the reason for each, searchable by filename and filterable by category. When there is nothing in it the page says "All Clear — No exceptions to handle. All documents processed successfully."
05 · Troubleshooting / notes
| What you see | Likely cause | What to do |
|---|---|---|
| Lots of failures at once from one source | A scanner setting, or a supplier changed their template | Fix the source before reprocessing |
| A file that isn't really a document | A cover sheet or signature image arrived as an attachment | Take it out of the queue |
| A document too long or too large | Over 50 pages or over 5 MB | Split it and send it again |
| A password-protected PDF | It can't be opened | Ask the sender for an unprotected copy |
06 · FAQ
Does an empty queue mean everything is fine?
No. A document that could not be read often finishes as Ready rather than arriving here. All Clear means nothing reached this queue — not that every document was read correctly.
What happens to a document that fails?
It makes no record, so nothing downstream knows about it. That is why an unread document is easy to miss and worth checking for directly.
Common questions
Once a day is enough. But also glance at anything that arrived recently, since this queue does not catch every kind of failure.