gRPC 3 INVALID_ARGUMENT vs 9 FAILED_PRECONDITION
Both gRPC 3 (INVALID_ARGUMENT) and 9 (FAILED_PRECONDITION) 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, 9 means that the operation was rejected because the system is not in a state required for the operation's execution. For example, deleting a non-empty directory.
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
The operation was rejected because the system is not in a state required for the operation's execution. For example, deleting a non-empty directory.
Wann Sie es sehen
The request is valid on its own, but the system's current state doesn't allow it — like trying to delete a non-empty directory or update a resource that has been modified concurrently.
Wie man es behebt
Bring the system into the required state before retrying. For example, empty the directory first, or re-read the resource to get the latest version before updating.
Wesentliche Unterschiede
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 9: The operation was rejected because the system is not in a state required for the operation's execution. For example, deleting a non-empty directory.
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 9 when the request is valid on its own, but the system's current state doesn't allow it — like trying to delete a non-empty directory or update a resource that has been modified concurrently.
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 9 (FAILED_PRECONDITION): Bring the system into the required state before retrying. For example, empty the directory first, or re-read the resource to get the latest version before updating.