MuleSoft · Rate Limiting: SLA-Based policy

429 Quota exceeded (Rate Limiting: SLA-Based)

Short answer

An API protected by the Rate Limiting: SLA-Based policy returns 429 when the client application has used up the quota of its SLA tier for the current window. Wait for the window to finish, or move the client to a tier with a higher limit.

VerifiedLast verified

01Error text

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

02Likely causes

  • The client application's requests exceeded the quota of its SLA tier. Requests are blocked until the current window finishes.

03How to fix it

  1. Wait until the current window finishes and retry.
  2. Check which SLA tier the client application's contract uses in API Manager, and whether a higher tier is appropriate.
  3. Turn on Expose Headers if clients need the rate limit headers to pace themselves.

iNotes

The Distributed option shares the quota across nodes only when Mule runs in HA cluster mode.

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.