> 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/tennis/live-data-scenarios-1/time-violations.md). # Time Violations \ Overview -------- If a player takes longer than 25 seconds between a point, they are in violation of tennis rules and the umpire will issue them a Time Violation. The following occurs as a result of the above Time Violations: **- First Offence:** Warning\ \&#xNAN;**- Second Offence - Receiver:** Point Penalty (The player's opposition are given the next point in the game)\ \&#xNAN;**- Second Offence - Server:** Serve Loss (The server is given a fault)\ \&#xNAN;**- Third and Subsequent Offences - Receiver:** Point Penalty (The player's opposition are given the next point in the game)\ \&#xNAN;**- Third and Subsequent Offences - Server:** Serve Loss (The server is given a fault) This will continue for as long as the umpire sees fit. If the Time Violations continue, then the umpire is within their right to start issue Code Violations (see [here](https://img-arena.gitbook.io/tennis/-M-nnUijRFbIhBBjSfUz/code-violations-game-penalties-and-defaults)). --- # 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/tennis/live-data-scenarios-1/time-violations.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.