HTTP 429 means a request rate limit has been reached. The response may include Retry-After, telling the client when to try again.
- Record the URL, time, response message, and any request identifier. Identify whether the application, API, or an upstream service issued the limit.
- Respect the stated retry delay. Stop rapid refreshes and overlapping retries.
- Compare the failure with scheduled jobs, imports, automated requests, and account activity.
- Reduce unnecessary request frequency or concurrency, then perform one deliberate retry after the waiting period.
A 429 does not by itself identify which account, resource, or counting rule was limited. Use the issuing service’s documented limits. Repeatedly changing credentials or disabling security controls is not a rate-limit fix.
Documentation for this guidance: www.rfc-editor.org — rfc6585.
