gRPC 1 CANCELLED vs 9 FAILED_PRECONDITION
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://statuscodefyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/entity//)Use the native HTML custom element.
Both gRPC 1 (CANCELLED) and 9 (FAILED_PRECONDITION) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. 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.
Description
The operation was cancelled, typically by the caller.
When You See It
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
How to Fix
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
Description
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.
When You See It
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.
How to Fix
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.
Key Differences
gRPC 1: The operation was cancelled, typically by the caller.
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 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 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.
When to Use Which
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 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.