gRPC 1 CANCELLED vs 3 INVALID_ARGUMENT
Both gRPC 1 (CANCELLED) and 3 (INVALID_ARGUMENT) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 3 means that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
Описание
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 client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
Когда вы это видите
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
Как исправить
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
Ключевые различия
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
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 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
Когда что использовать
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 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.