gRPC Status Codes

The operation completed successfully. Not an error; returned on success.

The operation was cancelled, typically by the caller.

An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known …

The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.

The deadline expired before the operation could complete. For operations that change the state of the system, this error may …

Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on …

The entity that a client attempted to create already exists. For example, a file or directory that the RPC was …

The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED …

Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.

The operation was rejected because the system is not in a state required for the operation's execution. For example, deleting …

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

The operation was attempted past the valid range. For example, seeking or reading past the end of a file.

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

An internal error occurred. This means that some invariant expected by the underlying system has been broken.

The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a …

Unrecoverable data loss or corruption has occurred.

The request does not have valid authentication credentials for the operation.