MuleSoft · Scatter-Gather router
MULE:COMPOSITE_ROUTING
Short answer
MULE:COMPOSITE_ROUTING means one or more routes of a Scatter-Gather router failed. The error gathers the errors from the failed routes and the Mule events from the routes that succeeded, so inspect its failures to find which route broke.
VerifiedLast verified
01Error text
Error type: MULE:COMPOSITE_ROUTING02Likely causes
- One or more errors occurred while routing a message. When a route fails, the Scatter-Gather component throws an error of this type.
- A route did not finish before the router's
timeoutexpired. That route throws aMULE:TIMEOUTerror, which is then collected here.
03How to fix it
- Read the failures the error carries. For example,
#[error.errorMessage.payload.failures['0'].errorType]returns the error type of the first route. - Fix the error inside the route that failed.
- To handle errors that a route's processors generate, use a Try scope in each route of the Scatter-Gather component.
- If routes time out, review the router's
timeoutattribute. It is in milliseconds, and a value of 0 or lower means no timeout. - Handle the remaining cases with an error handler of type
MULE:COMPOSITE_ROUTING.
04Official documentation
→Related errors
- MULE:RETRY_EXHAUSTEDMULE:RETRY_EXHAUSTED means every retry of an execution block failed, most often an Until Successful scope whose final retry did not succeed. Fix the error that the processors inside the scope keep raising, or adjust maxRetries and millisBetweenRetries.
- MULE:EXPRESSIONMULE:EXPRESSION means an error occurred while Mule evaluated a DataWeave expression. Find the expression named in the log, check the values it reads for nulls or wrong types, and add a default or a handler.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer