> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/too-many-attempts.md).
# Too many attempts
When the extension displays the message **“Too many attempts”**, you have reached the limit of the built-in rate limiter. This limiter controls network traffic per user to ensure the extension remains stable.
This error usually indicates that the database table contains too much data. The extension loads data in chunks of 1,000 rows, which means a user can load a maximum of 60,000 rows at once.
While it is possible to increase these limits, doing so comes with drawbacks—such as hitting memory limits or impacting performance. The recommended solution is to reduce the amount of data being loaded.
If you **wish** to increase the pagination size, alter the **'Chunk Size'** setting in the **Advanced settings** of the Management console:
---
# 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.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/too-many-attempts.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.
