> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/support-and-history/archived/deprecated-uof-error-date-schedule-read-timed-out-failed-api.md).
# \[Deprecated] UOF Error: Date Schedule Read Timed Out (Failed API)
**Error Description**
The log message indicates that a request was made to retrieve schedule data for April 17, 2023, from the specified API endpoint (`schedule.xml`). However, the request failed after taking approximately 30031 milliseconds (30.031 seconds). The failure reason is likely related to an exception (`ex`), which would provide more details about the specific error or issue encountered during the request execution.
```xml
INFO ] [] [scheduling-1] Request[DataFetcher]: https://global.api.betradar.com/v1/sports/en/schedules/2023-04-17/schedule.xml, response - FAILED(30031 ms), ex:
```
**Applies to**
UOF API
**Symptoms**
* Timeout of 30s on date schedule API endpoint
**Resolution**
* Increase allowed timeout
* Retry request as on second attempt the response can be cached by api backend and be served up much quicker.
---
# 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://docs.sportradar.com/uof/support-and-history/archived/deprecated-uof-error-date-schedule-read-timed-out-failed-api.md?ask=&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.