Setting this header on egress requests will cause Envoy to attempt to retry failed requests (number of retries defaults to 1, and can be controlled by x-envoy-max-retries header or the route config retry policy). gRPC retries are currently only supported for gRPC status codes in response headers. gRPC status codes in trailers will not trigger retry logic.

## Index

### Enumeration members

- CANCELLED
- DEADLINE_EXCEEDED
- RESOURCE_EXHAUSTED

## Enumeration members

### CANCELLED

CANCELLED: = "cancelled"

- Defined in envoy-grpc-request-params.ts:25

Envoy will attempt a retry if the gRPC status code in the response headers is “cancelled” (1)

### DEADLINE_EXCEEDED

DEADLINE_EXCEEDED: = "deadline-exceeded"

- Defined in envoy-grpc-request-params.ts:31

Envoy will attempt a retry if the gRPC status code in the response headers is “deadline-exceeded” (4)

### RESOURCE_EXHAUSTED

RESOURCE_EXHAUSTED: = "resource-exhausted"

- Defined in envoy-grpc-request-params.ts:37

Envoy will attempt a retry if the gRPC status code in the response headers is “resource-exhausted” (8)

Generated using TypeDoc