rate_limited

HTTP status: 429 · Code: rate_limited

Too many requests; wait for the number of seconds in Retry-After.

Why it happens

Too many requests of this kind in a short time, for example repeated sign in attempts for one email, or repeated email requests. Limits protect your users from guessing and spam.

How to fix

Wait the number of seconds in Retry-After (the SDK error carries it as retryAfter) before trying again, and tell the person when they can retry. Don’t retry in a loop.

Catch it in your code

Every SDK throws one error type for a failed call. Match on its code, which is always rate_limited for this error, never on the message.

JavaScript and Next.js

import { ErrorCode, OrvanoError } from '@orvano/js'

try {
  // your Orvano call
} catch (error) {
  if (error instanceof OrvanoError && error.code === ErrorCode.rateLimited) {
    // handle rate_limited
  } else {
    throw error
  }
}

Dart and Flutter

import 'package:orvano_flutter/orvano_flutter.dart'; // or orvano_dart on a server

try {
  // your Orvano call
} on OrvanoException catch (error) {
  if (error.code != ErrorCode.rateLimited) rethrow;
  // handle rate_limited
}

.NET

using Orvano;

try
{
    // your Orvano call
}
catch (OrvanoException error) when (error.Code == ErrorCode.RateLimited)
{
    // handle rate_limited
}

The error also carries the HTTP status (429), a message, and a request ID. Quote the request ID when you report a problem: the server logs it with the failure. See Errors for how errors work in every SDK, or every error code.