gRPC 0 OK vs 16 UNAUTHENTICATED
Both gRPC 0 (OK) and 16 (UNAUTHENTICATED) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. Meanwhile, 16 means that the request does not have valid authentication credentials for the operation.
Описание
The operation completed successfully. Not an error; returned on success.
Когда вы это видите
The RPC completed without any issues. This is the expected response for every successful gRPC call.
Как исправить
No fix needed — this indicates everything worked correctly.
Описание
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 0: The operation completed successfully. Not an error; returned on success.
gRPC 16: The request does not have valid authentication credentials for the operation.
You encounter 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
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 0 (OK): No fix needed — this indicates everything worked correctly. For 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).