MuleSoft · Spike Control policy

429 from the Spike Control policy

Short answer

An API protected by the Spike Control policy returns 429 when the request found no quota in the window and was still rejected after the configured number of retries. Slow the caller down, or adjust the policy's limit, delay and attempts.

VerifiedLast verified

01Error text

MuleSoft error
429 - The number of requests by HTTP APIs exceeded the configured limit. Request rejected after specified number of reattempts.

02Likely causes

  • The number of requests exceeded the configured limit for the time period.
  • When the window has no quota left, the request is queued and retried. It is rejected after Delay Attempts retries, each Delay Time in Milliseconds apart.

03How to fix it

  1. On the client side, lower the request rate or retry later.
  2. In API Manager, review Number of Reqs, Time Period, Delay Time in Milliseconds, Delay Attempts and Queuing Limit for the policy.
  3. Turn on Expose Headers to return X-Ratelimit-Remaining, X-Ratelimit-Limit and X-Ratelimit-Reset, so clients can pace themselves.

iNotes

WSDL APIs get 400 (SOAP 1.2) or 500 (SOAP 1.1) with the same wording. The docs say the policy exists to protect the API and its parameters should be set to the lowest possible value.

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.