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

MuleSoft error
Error type: HTTP:TOO_MANY_REQUESTS

02Likely causes

  • Too many requests were sent in a given amount of time.
  • By default, the Flow and Async scopes do not set a maxConcurrency limit, so a busy flow can call the server many times at once.

03How to fix it

  1. Find the server's documented rate limit, and compare it with how often the flow calls it.
  2. Limit how many events the flow processes at the same time by setting maxConcurrency on the <flow> element.
  3. Retry after a delay: wrap the request in an Until Successful scope and set millisBetweenRetries to a wait that fits the server's limit.
  4. Handle the failure with an error handler of type HTTP:TOO_MANY_REQUESTS so that rejected calls are logged or queued and not lost.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.