gRPC 0 OK vs 5 NOT_FOUND
Both gRPC 0 (OK) and 5 (NOT_FOUND) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. 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 completed successfully. Not an error; returned on success.
Cuándo lo verás
The RPC completed without any issues. This is the expected response for every successful gRPC call.
Cómo solucionarlo
No fix needed — this indicates everything worked correctly.
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 0: The operation completed successfully. Not an error; returned on success.
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 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
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 0 (OK): No fix needed — this indicates everything worked correctly. 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.