Status codes and their use in gRPC

gRPC uses a set of well defined status codes as part of the RPC API. All RPCs started at a client return a status object composed of an integer code and a string message. The server-side can choose the status it returns for a given RPC.

The gRPC client and server-side implementations may also generate and return status on their own when errors happen.
Only a subset of the pre-defined status codes are generated by the gRPC libraries. The following table lists these codes and summarizes the situations in which they are generated, either by the client or the server-side library implementation.

CaseCodeGenerated at Client or Server
Client Application cancelled the requestCANCELLEDBoth
Deadline expires before server returns statusDEADLINE_EXCEEDEDBoth
Method not found at serverUNIMPLEMENTEDServer
Server shutting downUNAVAILABLEServer
Server side application throws an exception (or does something other than returning a Status code to terminate an RPC)UNKNOWNServer
No response received before Deadline expires. This may occur either when the client is unable to send the request to the server or when the server fails to respond in time.DEADLINE_EXCEEDEDBoth
Some data transmitted (e.g., request metadata written to TCP connection) before connection breaksUNAVAILABLEClient
Could not decompress, but compression algorithm supported (Client -> Server)INTERNALServer
Could not decompress, but compression algorithm supported (Server -> Client)INTERNALClient
Compression mechanism used by client not supported at serverUNIMPLEMENTEDServer
Server temporarily out of resources (e.g., Flow-control resource limits reached)RESOURCE_EXHAUSTEDServer
Client does not have enough memory to hold the server responseRESOURCE_EXHAUSTEDClient
Flow-control protocol violationINTERNALBoth
Error parsing returned statusUNKNOWNClient
Incorrect Auth metadata ( Credentials failed to get metadata, Incompatible credentials set on channel and call, Invalid host set in :authority metadata, etc.)UNAUTHENTICATEDBoth
Request cardinality violation (method requires exactly one request but client sent some other number of requests)UNIMPLEMENTEDServer
Response cardinality violation (method requires exactly one response but server sent some other number of responses)UNIMPLEMENTEDClient
Error parsing response protoINTERNALClient
Error parsing request protoINTERNALServer

The following status codes are never generated by the library:

  • INVALID_ARGUMENT
  • NOT_FOUND
  • ALREADY_EXISTS
  • FAILED_PRECONDITION
  • ABORTED
  • OUT_OF_RANGE
  • DATA_LOSS