> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/how-to-add-an-error-page-to-your-shop.md).
# Error Page
## Introduction
Errors happen sometimes. From configuration issues to timeouts with external providers, there are plenty of reasons your shop might generate an error. Limio provides the ability to configure an error page, which a customer is redirected to when an error occurs.
This feature works with Page Builder v1 and v2.
*Beta: we'll be rolling this out across the whole app soon, but for now we're focusing on the errors that affect our customers most. Some might still slip through!*
## Configuration
Go to the pages section of your app and add a new page with the tag of /error. That's it! You can now use the page builder to configure your error page and users will start being redirected there as soon as it's published.
---
# 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.limio.com/product/settings/how-to-add-an-error-page-to-your-shop.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.