> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/origin-settings/origin-response-timeout.md).

# Origin Response Timeout

Learn how Origin Response Timeout controls how long the CDN waits for dynamic origin responses before returning an error.

The **Origin Response Timeout** feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery.\
It defines the maximum time the CDN waits for the origin to return an HTTP(S) response. When the origin exceeds this duration, the CDN stops waiting and returns a 504 Gateway Timeout, ensuring predictable behavior for dynamic workloads and preventing long wait times caused by slow or overloaded origins.

For configuration details, timeout behavior, and examples, refer to the main documentation:\
**Learn more in the** [**Origin Response Timeout documentation**](/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/origin-response-timeout.md)**.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/origin-settings/origin-response-timeout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.