gRPC 1 CANCELLED vs 7 PERMISSION_DENIED
Both gRPC 1 (CANCELLED) and 7 (PERMISSION_DENIED) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 7 means that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
الوصف
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 caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
متى تراه
The authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
كيفية الإصلاح
Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.
الفروق الرئيسية
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
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 7 when the authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
متى تستخدم أيًا منهما
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 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.