gRPC 1 CANCELLED vs 16 UNAUTHENTICATED
Both gRPC 1 (CANCELLED) and 16 (UNAUTHENTICATED) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 16 means that the request does not have valid authentication credentials for the operation.
説明
The operation was cancelled, typically by the caller.
このコードが表示される場合
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
解決方法
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
説明
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 1: The operation was cancelled, typically by the caller.
gRPC 16: The request does not have valid authentication credentials for the operation.
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 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 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 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).