server_busy

HTTP status: 503 · Code: server_busy

The server is too busy to check a password right now; retry after Retry-After.

Why it happens

The server is checking too many passwords at once. Checking a password is deliberately slow, so the server caps how many run together and turns the rest away instead of slowing everything down.

How to fix

Retry after the number of seconds in Retry-After. If it happens often under normal load, give the api service more CPU or run more api replicas.

Catch it in your code

Every SDK throws one error type for a failed call. Match on its code, which is always server_busy 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.serverBusy) {
    // handle server_busy
  } 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.serverBusy) rethrow;
  // handle server_busy
}

.NET

using Orvano;

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

The error also carries the HTTP status (503), 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.