Timeouts

Attach to:

Backend

Request timeouts Timeout A time limit for how long agentgateway will wait for a response from a backend before considering the request failed. Timeouts can be configured at the request or backend level. allow returning an error for requests that take too long to complete.

Route Timeouts

You can configure two types of timeouts on a route.

TimeoutDescription
requestTimeoutThe time from the start of an incoming request, until the end of the response headers is received. Note if there are retries, this includes the total time across retries.
backendRequestTimeoutThe time from the start of a request to a backend, until the end of the response headers are completed. Note this is per-request, so with retries this is a per-retry timeout.

For example:

timeout:
  requestTimeout: 1s

Backend Timeouts

In addition to route level timeouts, you can configure per-backend timeouts within the backend configuration section.

TimeoutDescription
requestTimeoutThe time from the start of an HTTP request to a backend until the response headers are completed.
connectTimeoutThe time from the start of a TCP connection to a backend until the connection is established.
http:
  requestTimeout: 1s
tcp:
  connectTimeout: 10s
Agentgateway assistant

Ask me anything about agentgateway configuration, features, or usage.

Note: AI-generated content might contain errors; please verify and test all returned information.

Tip: one topic per conversation gives the best results. Use the + button in the chat header to start a new conversation.

Switching topics? Starting a new conversation improves accuracy.
↑↓ navigate select esc dismiss

What could be improved?

Your feedback helps us improve assistant answers and identify docs gaps we should fix.

Need more help? Join us on Discord: https://discord.gg/y9efgEmppm

Want to use your own agent? Add the Solo MCP server to query our docs directly. Get started here: https://search.solo.io/.