gRPC 3 INVALID_ARGUMENT vs 13 INTERNAL
Both gRPC 3 (INVALID_ARGUMENT) and 13 (INTERNAL) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
Beschreibung
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
Wann Sie es sehen
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
Wie man es behebt
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
Beschreibung
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
Wann Sie es sehen
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Wie man es behebt
Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.
Wesentliche Unterschiede
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
You encounter 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Wann welchen verwenden
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.