If a flow does not define an exception strategy, whose strategy handles the exception?

If a flow does not define an exception strategy, whose strategy handles the exception?

• A. The global exception strategy
• B. The default exception strategy
• C. The strategy of the calling flow
• D. No exception handling is applied

Answer: (C)

In MuleSoft, exception handling follows the flow hierarchy. If a flow doesn’t define its own exception strategy, any error it encounters is not handled there but bubbles up to the flow that called it. That calling flow’s exception strategy then handles the exception. This means the responsibility for dealing with the error rests with the strategy of the flow that invoked the current one. Only if there’s no calling flow (or none in the chain has a strategy) would a global or default handler come into play.

In MuleSoft, exception handling follows the flow hierarchy. If a flow doesn’t define its own exception strategy, any error it encounters is not handled there but bubbles up to the flow that called it. That calling flow’s exception strategy then handles the exception. This means the responsibility for dealing with the error rests with the strategy of the flow that invoked the current one. Only if there’s no calling flow (or none in the chain has a strategy) would a global or default handler come into play.