> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/notices/feature-retirements/full-query-retirement.md). # Full Query Retirement ## What is happening? GRAX is retiring the Full Query functionality in favor of the newer, faster Query WHERE capability. * **October 31st, 2025**: All archives in **GRAX sandbox environments** will be transitioned to Query WHERE. * **November 14th, 2025**: All archives in **GRAX production environments** will be transitioned to Query WHERE. ## Why is this happening? GRAX has made significant improvements to optimize archive performance. Query WHERE provides several key benefits: * Automatically determines the optimal batch size * Delivers faster archive performance * Reduces timeout errors ## How does this impact me? You’ll continue archiving the same records as before — just faster and more efficiently. Our team will handle the transition from Full Query to Query WHERE archives for you. No action is required on your part. ## Timing GRAX support for Full Query ends on **November 14th, 2025**. ## Frequently Asked Questions ### Can I still add a LIMIT to my Query WHERE archives? Yes, but please note that adding a LIMIT may reduce performance, as Query WHERE automatically adjusts batch size based on system conditions. ### How do I get more information? If you have any questions or would like more details, please open a support ticket with our team. --- # 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://documentation.grax.com/notices/feature-retirements/full-query-retirement.md?ask=&goal= ``` `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.