exception flow end

Exceptional Flow End

Version: 17.07

Supported Since: 17.01

What is a Exceptional Flow End Processor?

A simple integration flow normally ends either

  • at a one-directional egress connector or

  • at the same bi-directional ingress connector that started the integration flow

But in a situation where none of the above two scenarios are possible, this processing element can be used to end an integration flow marking it as completed with an exception (i.e. marking it as failed). In such a case, the flow will fail with an IntegrationRuntimeException having the provided text as the exception message.

Since this processing element belongs to the set of basic processing elements, this will be available for every project by default.

exc end outports

Out Ports

On Exception

The message context will be sent to this outport if any exception occurred while processing


Exception Message *


The integration flow will end with an IntegrationRuntimeException, which will have the value of this parameter set as the message of the exception.

Sample Use Case

In the following use case, the requirement is to read a message from a SFTP server, perform some custom processing and then send it to a HTTP endpoint. When the response from the HTTP endpoint is received, a custom validation is performed on it and the flow should be marked as failed if the validation is failed.

exceptional flow end flow

To achieve the above requirement, the response path of the HTTP egress connector is connected to the custom processing element that performs the validation on the response. Then the "On Failure" outport of the processing element (which will receive the message context if the validation is failed) is connected to a Exceptional Flow End processing element that will mark the flow as failed.

In this topic
In this topic
Contact Us