MuleSoft · HTTP Connector
HTTP:TOO_MANY_REQUESTS
Short answer
HTTP: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.
VerifiedLast verified
01Error text
Error type: HTTP:TOO_MANY_REQUESTS02Likely causes
- Too many requests were sent in a given amount of time.
- By default, the Flow and Async scopes do not set a
maxConcurrencylimit, so a busy flow can call the server many times at once.
03How to fix it
- Find the server's documented rate limit, and compare it with how often the flow calls it.
- Limit how many events the flow processes at the same time by setting
maxConcurrencyon the<flow>element. - Retry after a delay: wrap the request in an Until Successful scope and set
millisBetweenRetriesto a wait that fits the server's limit. - Handle the failure with an error handler of type
HTTP:TOO_MANY_REQUESTSso that rejected calls are logged or queued and not lost.
04Official documentation
→Related errors
- HTTP:SERVICE_UNAVAILABLEHTTP:SERVICE_UNAVAILABLE means the server could not handle the request because it is down for maintenance or overloaded (HTTP 503). The fault is on the remote side, so retry after a delay and handle the error if the service stays down.
- 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.
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