MuleSoft · Mule runtime
Flow is unable to accept new events at this time
Short answer
This message means the flow is under back-pressure: it cannot take more events from its source right now. Check the flow's maxConcurrency and how long each event takes to process.
VerifiedLast verified
01Error text
Flow 'flowName' is unable to accept new events at this time02Likely causes
- A problem of overloading occurred at the source level, which Mule calls back-pressure (
MULE:FLOW_BACK_PRESSURE). - The flow, or the system's capacity, limits how many events can be processed at the same time.
- A
maxConcurrencyvalue set on the flow is lower than the incoming load needs.
03How to fix it
- Check whether
maxConcurrencyis set on the<flow>element. By default, the Flow and Async scopes do not set a limit. - If you set it, review the value. The docs recommend the default settings unless you have a reason to change them.
- Shorten the processing time per event, so the flow frees capacity sooner.
- Check what the flow's source does under back-pressure. The actions are specific to each connector's source.
04Official documentation
→Related errors
- HTTP:TOO_MANY_REQUESTSHTTP:TOO_MANY_REQUESTS means the server received too many requests from your app in a given amount of time (HTTP 429). Send fewer calls at once and retry after a delay.
- MULE:FATAL_JVM_ERRORMULE:FATAL_JVM_ERROR means a fatal error occurred in the JVM, such as a stack overflow. It cannot be handled in a flow, and the only safe recovery after a VirtualMachineError is to restart the Mule runtime instance.
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