gRPC

gRPC 12 UNIMPLEMENTED vs 13 INTERNAL

Both gRPC 12 (UNIMPLEMENTED) and 13 (INTERNAL) belong to the gRPC Status Codes category. 12 indicates that the operation is not implemented or is not supported/enabled in this service. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.

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.

Description

An internal error occurred. This means that some invariant expected by the underlying system has been broken.

When You See It

A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.

How to Fix

Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.

Key Differences

1.

gRPC 12: The operation is not implemented or is not supported/enabled in this service.

2.

gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.

3.

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.

4.

You encounter 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.

When to Use Which

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. For 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.

Learn More