gRPC 4 DEADLINE_EXCEEDED vs 11 OUT_OF_RANGE
Both gRPC 4 (DEADLINE_EXCEEDED) and 11 (OUT_OF_RANGE) belong to the gRPC Status Codes category. 4 indicates that the deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. Meanwhile, 11 means that the operation was attempted past the valid range. For example, seeking or reading past the end of a file.
Description
The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
When You See It
The RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
How to Fix
Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying.
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 4: The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
You encounter 4 when the RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
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 4 (DEADLINE_EXCEEDED): Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying. 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.