> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/faq-and-troubleshooting/troubleshooting/error-messages.md). # Error messages ### About Error Messages Deciphering PageFly Error Messages: A Guide to Smooth Sailing Don't let cryptic error messages derail your PageFly workflow! This Error Messages overview equips you to understand and resolve the most common issues you might encounter while editing your online store. Facing an infinite loading loop on your PageFly page list, or struggling with a "Page Size Limit" error? This section provides clear explanations for various error messages, along with actionable solutions. Whether you're unsure about how many elements to include on a page, encountering difficulties importing data, or facing an "Unknown error," this guide empowers you to troubleshoot the issue efficiently. By understanding the meaning behind these messages, you can overcome these hurdles and ensure a smooth and productive PageFly editing experience. ### Related Resources * [Frequently Asked Questions](https://help.pagefly.io/manual/affiliate-program-faq/) * [PageFly Manual | Guides and tutorials to best use PageFly](https://help.pagefly.io/) * [How To Upgrade PageFly Plan](https://help.pagefly.io/manual/how-to-upgrade-pagefly-plan/) * [New Slide Show Elements. Uninstall Policy Update](https://pagefly.io/blogs/shopify/pagefly-4-7-0-new-slide-show-elements-uninstall-policy-update) --- # 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://help.pagefly.io/faq-and-troubleshooting/troubleshooting/error-messages.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.