gRPC 6 ALREADY_EXISTS vs 12 UNIMPLEMENTED
Both gRPC 6 (ALREADY_EXISTS) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 6 indicates that the entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
Description
The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
When You See It
A create operation failed because a resource with the same unique identifier or name already exists in the system.
How to Fix
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
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 6: The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
You encounter 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
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 6 (ALREADY_EXISTS): Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating. 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.