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

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-f70fa54c95ad84d5972d357ee1d3b7598d4d3f1c%2Fimage%20(189).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.limio.com/product/settings/how-to-add-an-error-page-to-your-shop.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.
