package google.rpc

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message BadRequest

error_details.proto:175

Describes violations in a client request. This error type focuses on the syntactic aspects of the request.

message BadRequest.FieldViolation

error_details.proto:177

A message type used to describe a single bad request field.

Used in: BadRequest

message DebugInfo

error_details.proto:102

Describes additional debugging info.

message ErrorInfo

error_details.proto:55

Describes the cause of the error with structured details. Example of an error when contacting the "pubsub.googleapis.com" API when it is not enabled: ```text,json { "reason": "API_DISABLED" "domain": "googleapis.com" "metadata": { "resource": "projects/123", "service": "pubsub.googleapis.com" } } ``` This response indicates that the pubsub.googleapis.com API is not enabled. Example of an error that is returned when attempting to create a Spanner instance in a region that is out of stock: ```text,json { "reason": "STOCKOUT" "domain": "spanner.googleapis.com", "metadata": { "availableRegions": "us-central1,us-east2" } } ```

message Help

error_details.proto:280

Provides links to documentation or for performing an out of band action. For example, if a quota check failed with an error indicating the calling project hasn't enabled the accessed service, this can contain a URL pointing directly to the right place in the developer console to flip the bit.

error_details.proto:282

Describes a URL link.

Used in: Help

message LocalizedMessage

error_details.proto:296

Provides a localized error message that is safe to return to the user which can be attached to an RPC error.

Used in: BadRequest.FieldViolation

message PreconditionFailure

error_details.proto:149

Describes what preconditions have failed. For example, if an RPC failed because it required the Terms of Service to be acknowledged, it could list the terms of service violation in the PreconditionFailure message.

message PreconditionFailure.Violation

error_details.proto:151

A message type used to describe a single precondition failure.

Used in: PreconditionFailure

message QuotaFailure

error_details.proto:121

Describes how a quota check failed. For example if a daily limit was exceeded for the calling project, a service could respond with a QuotaFailure detail containing the project id and the description of the quota limit that was exceeded. If the calling project hasn't enabled the service in the developer console, then a service could respond with the project id and set `service_disabled` to true. Also see RetryInfo and Help types for other details about handling a quota failure.

message QuotaFailure.Violation

error_details.proto:124

A message type used to describe a single quota violation. For example, a daily quota or a custom quota that was exceeded.

Used in: QuotaFailure

message RequestInfo

error_details.proto:241

Contains metadata about the request that clients can attach when filing a bug or providing other forms of feedback.

message ResourceInfo

error_details.proto:252

Describes the resource that is being accessed.

message RetryInfo

error_details.proto:96

Describes when the clients can retry a failed request. Clients could ignore the recommendation here or retry when this information is missing from error responses. It's always recommended that clients should use exponential backoff when retrying. Clients should wait until `retry_delay` amount of time has passed since receiving the error response before retrying. If retrying requests also fail, clients should use an exponential backoff scheme to gradually increase the delay between retries based on `retry_delay`, until either a maximum number of retries have been reached or a maximum retry delay cap has been reached.

message Status

status.proto:35

The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).