Skip to main content

Error exit

End point of a refused branch: when an error reaches it, the job stops with the "⛔ Rejected" status and the message the error carries. It is how a pipeline says "this document is not for me" instead of letting the job finish normally with zero annotations.

It is always fed by an Error message node (which sets the message), or by the "error" output of a Pipeline node. A pipeline holds a single error exit; several error messages can lead to it.

Ports​

  • Input (left, error type).
  • No output.

Configuration​

None: the message comes from the node feeding it.

What the user sees​

The Rejected status is distinct from Error (a technical failure) and Blocked (an interceptor): there is nothing to fix, the pipeline refused the document on purpose. The message is shown:

  • in the application's history, under the status;
  • in the editor's test panel;
  • in the completion email and in Microsoft Teams;
  • through the API, in the job's error_message field (status is rejected), and over MCP.

In a chat pipeline, the message is the answer shown to the user.

A rejected job produces no document and is not billed.

In a sub-pipeline​

A pipeline with an error exit adds an "error" output to every Pipeline node calling it. Left unwired, the error goes up and rejects the calling job too, with the sub-pipeline's message; wired, it is intercepted (for instance to rewrite the message).

Examples​

  • A Switch's Default route → Error message "Only employment contracts are accepted" → Error exit.
  • The MIME filter's Image output → Error message "Send the ID document as a PDF, not a photo" → Error exit.