MuleSoft · Mule runtime
MULE:TIMEOUT
Short answer
MULE:TIMEOUT means a timeout occurred while Mule processed a message, for example a Scatter-Gather route that did not finish before the router's timeout. Speed up the slow route or raise the timeout.
VerifiedLast verified
01Error text
Error type: MULE:TIMEOUT02Likely causes
- A timeout occurred while processing a message.
- A Scatter-Gather component has a
timeout, and a route did not complete processing before it expired. That route throwsMULE:TIMEOUT.
03How to fix it
- Find the route or component that runs long.
- Shorten its work, or raise the
timeoutattribute of the Scatter-Gather. It is in milliseconds, and a value of 0 or lower means no timeout. - Use a Try scope in each route to handle errors raised inside that route.
- Handle the collected error with a handler of type
MULE:COMPOSITE_ROUTING, which is what the Scatter-Gather throws when routes fail.
04Official documentation
→Related errors
- MULE:COMPOSITE_ROUTINGMULE: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.
- HTTP:TIMEOUTHTTP:TIMEOUT means a request sent by the HTTP Request operation timed out before the response arrived. The wait is set by Response Timeout, which is 10000 milliseconds unless you change it, so raise it or make the remote service answer faster.
- VM:QUEUE_TIMEOUTVM:QUEUE_TIMEOUT means a VM Connector operation waited for a queue longer than its Timeout, which is 5 seconds by default. Raise the Timeout, or make the flow that consumes the queue finish sooner.
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