MuleSoft · Until Successful scope
MULE:RETRY_EXHAUSTED
Short answer
MULE: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.
VerifiedLast verified
01Error text
Message: 'until-successful' retries exhausted.
Error type: MULE:RETRY_EXHAUSTED02Likely causes
- The retries of an execution block have been exhausted. If the final retry of an Until Successful scope does not succeed, the scope produces this error.
- The processors inside the scope fail on every attempt, so retrying alone cannot succeed.
- The retry settings give the remote system too little time to recover:
maxRetriesis too low ormillisBetweenRetriesis too short.
03How to fix it
- Find the underlying error. The log shows a line such as
Retrying execution of event, attempt 1 of 5for each attempt. - Fix that underlying error first, for example the connectivity or timeout problem of the operation inside the scope.
- If the failure is temporary, raise
maxRetriesormillisBetweenRetrieson the Until Successful scope.millisBetweenRetriesdefaults to 60000, which is one minute. - Handle the final failure with an error handler of type
MULE:RETRY_EXHAUSTED, for example<on-error-continue type="RETRY_EXHAUSTED">.
04Official documentation
→Related errors
- HTTP:CONNECTIVITYHTTP:CONNECTIVITY means the HTTP Request operation could not establish a connection to the server. Check the host, port, protocol and TLS settings, and add your own retry because the operation does not use the reconnection strategy for retries.
- 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.
- 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.
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