gRPC 4 DEADLINE_EXCEEDED vs 7 PERMISSION_DENIED
Both gRPC 4 (DEADLINE_EXCEEDED) and 7 (PERMISSION_DENIED) belong to the gRPC Status Codes category. 4 indicates that the deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. Meanwhile, 7 means that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
Description
The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
Quand vous le voyez
The RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
Comment résoudre
Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying.
Description
The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
Quand vous le voyez
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.
Comment résoudre
Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.
Différences clés
gRPC 4: The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
You encounter 4 when the RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
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.
Quand utiliser lequel
For 4 (DEADLINE_EXCEEDED): Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying. For 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.