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.
Beschreibung
The operation was cancelled, typically by the caller.
Wann Sie es sehen
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
Wie man es behebt
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
Beschreibung
The request does not have valid authentication credentials for the operation.
Wann Sie es sehen
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.
Wie man es behebt
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
Wesentliche Unterschiede
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.
Wann welchen verwenden
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).