gRPC status codes

YDB provides the gRPC API, which you can use to manage your database resources and data. The following table describes the gRPC status codes:

Code	Status	Retryability	Backoff strategy	Recreate session
0	OK	–	–	–
1	CANCELLED	conditionally-retryable	fast	yes
2	UNKNOWN	non-retryable	–	yes
3	INVALID_ARGUMENT	non-retryable	–	yes
4	DEADLINE_EXCEEDED	conditionally-retryable	fast	yes
5	NOT_FOUND	non-retryable	–	yes
6	ALREADY_EXISTS	non-retryable	–	yes
7	PERMISSION_DENIED	non-retryable	–	yes
8	RESOURCE_EXHAUSTED	retryable	slow	no
9	FAILED_PRECONDITION	non-retryable	–	yes
10	ABORTED	retryable	instant	yes
11	OUT_OF_RANGE	non-retryable	–	no
12	UNIMPLEMENTED	non-retryable	–	yes
13	INTERNAL	conditionally-retryable	fast	yes
14	UNAVAILABLE	conditionally-retryable	fast	yes
15	DATA_LOSS	non-retryable	–	yes
16	UNAUTHENTICATED	non-retryable	–	yes

0: OK

Not an error; returned on success.

The operation was cancelled, typically by the caller.

Unknown error. For example, this error may be returned when a Status value received from another address space belongs to an error space that is not known in this address space. Errors raised by APIs that do not return enough error information may also be converted to this error.

The client specified an invalid argument. Unlike FAILED_PRECONDITION, INVALID_ARGUMENT indicates arguments that are problematic regardless of the system state (e.g., a malformed file name).

The query was not processed within the specified client timeout, or a network issue occurred.

Check the specified timeout, network access, endpoint, and other network settings. Reduce the query rate and optimize queries.

A requested scheme object (for example, a table or directory) was not found.

The scheme object that a client attempted to create (e.g., file or directory) already exists.

The caller does not have permission to execute the specified operation.

There are not enough resources available to fulfill the query.

Reduce the query rate and check client balancing.

The query cannot be executed in the current state (for example, inserting data into a table with an existing key).

Fix the state or query, then retry.

The operation was aborted, typically due to a concurrency issue, such as a transaction abort.

The operation was attempted past the valid range. Unlike INVALID_ARGUMENT, this error indicates a problem that may be fixed if the system state changes.

The operation is not implemented, supported, or enabled in this service.

Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for significant problems.

The service is currently unavailable. This is most likely a transient condition that can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.

Unrecoverable data loss or corruption.

The request did not have valid authentication credentials.

Retry the request with valid authentication credentials.