Skip to main content

Error message

Turns a branch into an error carrying your message, to wire to the Error exit: the job then stops with the "Rejected" status and that message.

Ports​

  • Input (left) — accepts what you may want to refuse:
    • the document (a Switch route, typically "Default");
    • an output of the MIME filter (Image, Scanned PDF or Other);
    • the "error" output of a Pipeline node: the sub-pipeline's message is then replaced by yours (the original stays visible in the test panel's node details).
  • Output (right, error type) — to the Error exit only.

Configuration​

  • Message — required. It is the text read by the user whose document is refused: write it for them, saying what is wrong and what to do ("Only employment contracts are accepted by this portfolio").

The editor refuses to save an empty message, or an Error message node not wired to the Error exit — it would refuse nothing.

MIME filter: when the error happens​

Support documents are sorted before the graph runs. If one falls into a category wired to an error message, the job is rejected before any other step (in particular before OCR, which is therefore not paid for). An image whose Image output leads to the error exit is accepted at upload even without an OCR node: the job refuses it, with your message.

In a chat pipeline, an attachment stays attached to the whole conversation: an image refused by the Image output is therefore refused as soon as the attachment is sent, with your message. The Scanned PDF and Other outputs do not apply to chat attachments.