gRPC 5 NOT_FOUND vs 11 OUT_OF_RANGE
Both gRPC 5 (NOT_FOUND) and 11 (OUT_OF_RANGE) belong to the gRPC Status Codes category. 5 indicates that some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist. Meanwhile, 11 means that the operation was attempted past the valid range. For example, seeking or reading past the end of a file.
Description
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
When You See It
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
How to Fix
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
Description
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
When You See It
A pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
How to Fix
Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.
Key Differences
gRPC 5: Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
You encounter 5 when the resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
You encounter 11 when a pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
When to Use Which
For 5 (NOT_FOUND): Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client. For 11 (OUT_OF_RANGE): Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.