> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-interactive-reports-cp/build-large-reports/row-limits-and-query-timeouts-build-large-reports-in-pir.md).

# Row limits and query timeouts

You can limit the number of rows that are displayed in your report during your design process in Interactive Reports by setting the **Row Limit** options in the **Interactive Toolbar**. You can also limit the number of seconds a query runs before a timeout occurs by selecting**Query Timeout** and specifying the number of seconds in the Query Settings dialog box. Imposing row limits and time-outs on queries is important to avoid out-of-memory errors, or processes that consume too many resources on the database server.

If you have exceeded the system maximum of rows, a help message appears to guide you.

![Interactive Report Row Limit Reached message](/files/eQzmsQgqld61GyzkgEwe)

To define the system maximum row limit for your Interactive Reports, ask your system administrator to review the **Administer Pentaho Data Integration and Analytics** document for further information.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pba/10.2-analytics/pentaho-interactive-reports-cp/build-large-reports/row-limits-and-query-timeouts-build-large-reports-in-pir.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.