gRPC 0 OK vs 2 UNKNOWN
Both gRPC 0 (OK) and 2 (UNKNOWN) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. Meanwhile, 2 means that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
Description
The operation completed successfully. Not an error; returned on success.
When You See It
The RPC completed without any issues. This is the expected response for every successful gRPC call.
How to Fix
No fix needed — this indicates everything worked correctly.
Description
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
When You See It
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
How to Fix
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
Key Differences
gRPC 0: The operation completed successfully. Not an error; returned on success.
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
You encounter 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
When to Use Which
For 0 (OK): No fix needed — this indicates everything worked correctly. For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.