A Mule application has a global error handler defined, and it is noted that the processors inside the global error handler are triggered multiple times even if there is only one exception that happened in the application.
SAMPLE FLOW DESIGN
The "On Error Propagate" re-throws the exception after processors have executed. This is causing the "Flow Reference" in the parent Flow to throw an exception again and the exception is being caught by the Global Error handler again as no flow-level handler is defined.
Catch the exception at Flow level and only re-throw the error when it can not be handled at Flow level to the parent Flow.
Design the Global Error Handler to use "On Error Continue" instead of "Global Error Handler" to avoid recursive invocation of the error handler. The Global Error Handler is meant to be a safety net to handle an error that is unexpected at design time and avoid the raw error propagating to the client side instead of a silver bullet to catch and resolve all errors.
001121687

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.