gRPC 1 CANCELLED vs 12 UNIMPLEMENTED
Both gRPC 1 (CANCELLED) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
Description
The operation was cancelled, typically by the caller.
When You See It
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
How to Fix
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
Description
The operation is not implemented or is not supported/enabled in this service.
When You See It
The client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
How to Fix
Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.
Key Differences
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
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 12 when the client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
When to Use Which
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 12 (UNIMPLEMENTED): Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.