MuleSoft · Rate Limiting policy

429 Quota exceeded

Short answer

An API protected by the Rate Limiting policy returns 429 Quota exceeded when the request quota for the current time window is used up. Requests are blocked until the window finishes, so wait for the window to reset or raise the limit in the policy.

VerifiedLast verified

01Error text

MuleSoft error
429 - Quota exceeded, requests are blocked until the current window finishes

02Likely causes

  • The request quota for the current window is used up.

03How to fix it

  1. Wait for the current window to finish. Requests are blocked until then.
  2. Turn on Expose Headers in the policy to let clients see X-Ratelimit-Remaining, X-Ratelimit-Limit and X-Ratelimit-Reset. They are off by default.
  3. Raise the number of requests or change the time period in the policy if the limit is too low for legitimate traffic.
  4. To protect a backend from bursts, the docs point to the Spike Control policy.

iNotes

For WSDL APIs on Mule, the policy returns 400 for SOAP 1.2 and 500 for SOAP 1.1 when the quota is exceeded. The docs advise longer windows in clusters.

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.