MuleSoft · Mule runtime
MULE:REDELIVERY_EXHAUSTED
Short answer
MULE:REDELIVERY_EXHAUSTED means a source's maximum attempts to reprocess a message have been used up. Fix the error that makes the flow fail on that message, then review the Max Redelivery Count of the redelivery policy.
VerifiedLast verified
01Error text
Error type: MULE:REDELIVERY_EXHAUSTED02Likely causes
- The maximum attempts to reprocess a message from a source have been exhausted.
- The source has a redelivery policy, and the same message was processed unsuccessfully more times than Max Redelivery Count allows.
03How to fix it
- Find the error the flow raises for that message in the earlier log entries.
- Fix that error, or route messages that cannot be processed to a place where they can be inspected.
- Review Max Redelivery Count on the source's redelivery policy.
- Handle the failure with an error handler of type
REDELIVERY_EXHAUSTED.
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.
- 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