gRPC 6 ALREADY_EXISTS vs 16 UNAUTHENTICATED
Both gRPC 6 (ALREADY_EXISTS) and 16 (UNAUTHENTICATED) 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, 16 means that the request does not have valid authentication credentials for the operation.
説明
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.
このコードが表示される場合
A create operation failed because a resource with the same unique identifier or name already exists in the system.
解決方法
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
説明
The request does not have valid authentication credentials for the operation.
このコードが表示される場合
No credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
解決方法
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
主な違い
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 16: The request does not have valid authentication credentials for the operation.
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 16 when no credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
どちらをいつ使うか
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 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).