internal_error
HTTP status: 500 · Code: internal_error
Any failure the server did not expect.
Why it happens
Section titled “Why it happens”Something failed on the server that it did not expect: a bug, a database that went away, or a dependency that broke. The response never says more, so no internal detail leaks to a caller.
How to fix
Section titled “How to fix”Retry once; a short outage often clears. If it keeps happening, look in the api logs for the request ID from the error (docker compose logs api on a local or Compose install) and report it with that ID on GitHub.
Catch it in your code
Section titled “Catch it in your code”Every SDK throws one error type for a failed call. Match on its code, which is always internal_error for this error, never on the message.
import { ErrorCode, OrvanoError } from '@orvano/js'
try { // your Orvano call} catch (error) { if (error instanceof OrvanoError && error.code === ErrorCode.internalError) { // handle internal_error } else { throw error }}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.internalError) rethrow; // handle internal_error}using Orvano;
try{ // your Orvano call}catch (OrvanoException error) when (error.Code == ErrorCode.InternalError){ // handle internal_error}The error also carries the HTTP status (500), 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.