gRPC 7 PERMISSION_DENIED vs 15 DATA_LOSS
Both gRPC 7 (PERMISSION_DENIED) and 15 (DATA_LOSS) belong to the gRPC Status Codes category. 7 indicates that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead. Meanwhile, 15 means that unrecoverable data loss or corruption has occurred.
Beschreibung
The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
Wann Sie es sehen
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.
Wie man es behebt
Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.
Beschreibung
Unrecoverable data loss or corruption has occurred.
Wann Sie es sehen
Critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
Wie man es behebt
Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.
Wesentliche Unterschiede
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
gRPC 15: Unrecoverable data loss or corruption has occurred.
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.
You encounter 15 when critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
Wann welchen verwenden
For 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side. For 15 (DATA_LOSS): Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.