project_not_ready

HTTP status: 409 · Code: project_not_ready

The project is still provisioning, or provisioning failed.

Why it happens

The project is still being set up, or its setup failed. A new project takes a few seconds to provision its database.

How to fix

Wait a few seconds and try again. If the project’s overview in the console shows that setup failed, check the worker logs, then retry setup from the console or create the project again.

Catch it in your code

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

.NET

using Orvano;

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

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