FailedExchange component
The FailedExchange component is always present in the Error Route. When a flow is running all failed exchanges are sent to the FailedExchange component. The FailedExchange component can be configured to retry failed exchanges several times with a delay in between. Ultimately, if the exchanges continue to fail, it will cease retrying and simply hand over the exchange payload to the next component in the Error Route.
Exceptions originating in the Error Route are only shown in the Flow logs. They are not handled by the FailedExchange component in the Error Route to prevent infinite loops. The typical use case for error handling in the Error Route should be simpler and less error-prone than for regular flows.
Refer to our Using exceptions guide for a full reference on exceptions and the expressions to retrieve them from a failed exchange.
Configuration
The FailedExchange component has the following configuration options:
maximumRedeliveries
Set the number of attempts to retry failing exchanges, default is 0.
If maxiumRedeliveries is set to 0, then no attempts are made to retry the exchange.
redeliveryInterval
Set the time in milliseconds between each retry.