gRPC 1 CANCELLED vs 5 NOT_FOUND
Both gRPC 1 (CANCELLED) and 5 (NOT_FOUND) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 5 means that some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
Descripción
The operation was cancelled, typically by the caller.
Cuándo lo verás
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
Cómo solucionarlo
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
Descripción
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
Cuándo lo verás
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
Cómo solucionarlo
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
Diferencias clave
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 5: Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
You encounter 1 when the client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
You encounter 5 when the resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
Cuándo usar cada uno
For 1 (CANCELLED): If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain. For 5 (NOT_FOUND): Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.