> 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](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-140bf2a64862c960dace1683530b77574ffaa024%2FPUC_PIR_Row_Limit_Reached.png?alt=media)

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

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

```
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=<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.