rate_limited
What happened
Section titled “What happened”Too many requests. Please wait a moment and try again.
Technical background
Section titled “Technical background”RateLimitError (HTTP 429) fires when a request exceeds a configured
limit: the per-handler rateLimit, the per-IP limit in front of the API,
or the limit of an r.httpRoute. details names the bucket, the limit
per windowSeconds, remaining, retryAfterSeconds and resetAt. The
HTTP layer sets Retry-After and the X-RateLimit-* headers from the same
values, so a client can show “try again in N seconds” without another
request. The auth routes (sign-in, password reset and similar) answer a
plain { "isSuccess": false, "error": "rate_limited" } with 429.
See rate-limiting for the
configuration. If the limiter itself is down, the code is
rate_limit_unavailable.