If not specified, will use the timeout set in theHttpRouteAction field.
If timeout in the HttpRouteAction field is not set, this field
uses the largest timeout
among all backend services associated with the route.
Not supported when the URL map is bound to a target gRPC proxy that
has the validateForProxyless field set to true.
If not specified, will use the timeout set in theHttpRouteAction field.
If timeout in the HttpRouteAction field is not set, this field
uses the largest timeout
among all backend services associated with the route.
Not supported when the URL map is bound to a target gRPC proxy that
has the validateForProxyless field set to true.
Specifies one or more conditions when this retry policy applies. Valid
values are:
- 5xx: retry is attempted if the instance or endpoint
responds with any 5xx response code, or if the instance or
endpoint does not respond at all. For example, disconnects, reset, read
timeout, connection failure, and refused streams.
- gateway-error: Similar to 5xx, but only
applies to response codes 502, 503 or504.
- connect-failure: a retry is attempted on failures
connecting to the instance or endpoint. For example, connection
timeouts.
- retriable-4xx: a retry is attempted if the instance
or endpoint responds with a 4xx response code.
The only error that you can retry is error code 409.
- refused-stream: a retry is attempted if the instance
or endpoint resets the stream with a REFUSED_STREAM error
code. This reset type indicates that it is safe to retry.
- cancelled: a retry is attempted if the gRPC status
code in the response header is set to cancelled.
- deadline-exceeded: a retry is attempted if the gRPC
status code in the response header is set todeadline-exceeded.
- internal: a retry is attempted if the gRPC
status code in the response header is set tointernal.
- resource-exhausted: a retry is attempted if the gRPC
status code in the response header is set toresource-exhausted.
- unavailable: a retry is attempted if the gRPC
status code in the response header is set tounavailable.
Only the following codes are supported when the URL map is bound to
target gRPC proxy that has validateForProxyless field set to true.
Specifies one or more conditions when this retry policy applies. Valid
values are:
- 5xx: retry is attempted if the instance or endpoint
responds with any 5xx response code, or if the instance or
endpoint does not respond at all. For example, disconnects, reset, read
timeout, connection failure, and refused streams.
- gateway-error: Similar to 5xx, but only
applies to response codes 502, 503 or504.
- connect-failure: a retry is attempted on failures
connecting to the instance or endpoint. For example, connection
timeouts.
- retriable-4xx: a retry is attempted if the instance
or endpoint responds with a 4xx response code.
The only error that you can retry is error code 409.
- refused-stream: a retry is attempted if the instance
or endpoint resets the stream with a REFUSED_STREAM error
code. This reset type indicates that it is safe to retry.
- cancelled: a retry is attempted if the gRPC status
code in the response header is set to cancelled.
- deadline-exceeded: a retry is attempted if the gRPC
status code in the response header is set todeadline-exceeded.
- internal: a retry is attempted if the gRPC
status code in the response header is set tointernal.
- resource-exhausted: a retry is attempted if the gRPC
status code in the response header is set toresource-exhausted.
- unavailable: a retry is attempted if the gRPC
status code in the response header is set tounavailable.
Only the following codes are supported when the URL map is bound to
target gRPC proxy that has validateForProxyless field set to true.
The bytes of the retryConditions at the given index.
getRetryConditionsCount()
publicintgetRetryConditionsCount()
Specifies one or more conditions when this retry policy applies. Valid
values are:
- 5xx: retry is attempted if the instance or endpoint
responds with any 5xx response code, or if the instance or
endpoint does not respond at all. For example, disconnects, reset, read
timeout, connection failure, and refused streams.
- gateway-error: Similar to 5xx, but only
applies to response codes 502, 503 or504.
- connect-failure: a retry is attempted on failures
connecting to the instance or endpoint. For example, connection
timeouts.
- retriable-4xx: a retry is attempted if the instance
or endpoint responds with a 4xx response code.
The only error that you can retry is error code 409.
- refused-stream: a retry is attempted if the instance
or endpoint resets the stream with a REFUSED_STREAM error
code. This reset type indicates that it is safe to retry.
- cancelled: a retry is attempted if the gRPC status
code in the response header is set to cancelled.
- deadline-exceeded: a retry is attempted if the gRPC
status code in the response header is set todeadline-exceeded.
- internal: a retry is attempted if the gRPC
status code in the response header is set tointernal.
- resource-exhausted: a retry is attempted if the gRPC
status code in the response header is set toresource-exhausted.
- unavailable: a retry is attempted if the gRPC
status code in the response header is set tounavailable.
Only the following codes are supported when the URL map is bound to
target gRPC proxy that has validateForProxyless field set to true.
Specifies one or more conditions when this retry policy applies. Valid
values are:
- 5xx: retry is attempted if the instance or endpoint
responds with any 5xx response code, or if the instance or
endpoint does not respond at all. For example, disconnects, reset, read
timeout, connection failure, and refused streams.
- gateway-error: Similar to 5xx, but only
applies to response codes 502, 503 or504.
- connect-failure: a retry is attempted on failures
connecting to the instance or endpoint. For example, connection
timeouts.
- retriable-4xx: a retry is attempted if the instance
or endpoint responds with a 4xx response code.
The only error that you can retry is error code 409.
- refused-stream: a retry is attempted if the instance
or endpoint resets the stream with a REFUSED_STREAM error
code. This reset type indicates that it is safe to retry.
- cancelled: a retry is attempted if the gRPC status
code in the response header is set to cancelled.
- deadline-exceeded: a retry is attempted if the gRPC
status code in the response header is set todeadline-exceeded.
- internal: a retry is attempted if the gRPC
status code in the response header is set tointernal.
- resource-exhausted: a retry is attempted if the gRPC
status code in the response header is set toresource-exhausted.
- unavailable: a retry is attempted if the gRPC
status code in the response header is set tounavailable.
Only the following codes are supported when the URL map is bound to
target gRPC proxy that has validateForProxyless field set to true.
If not specified, will use the timeout set in theHttpRouteAction field.
If timeout in the HttpRouteAction field is not set, this field
uses the largest timeout
among all backend services associated with the route.
Not supported when the URL map is bound to a target gRPC proxy that
has the validateForProxyless field set to true.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-01-09 UTC."],[],[]]