> 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.md). # Troubleshooting ### About Troubleshooting Troubleshooting PageFly Hiccups: A Guide to a smooth editing experience! Ever experienced a blank space at the top of your page, or encountered error messages while adding content? Often, these hiccups stem from conflicts within your Shopify theme files or exceeding data limits. This Troubleshooting section will provide you with a clear explanation for these errors, along with easy-to-follow solutions. By familiarizing yourself with these solutions, you can overcome these minor roadblocks and ensure a smooth and efficient PageFly editing experience. Our PageFly Support Team is always trying our best to help you anytime you need so do not hesitate to contact us! You can check the video tutorial on getting started with PageFly below: {% embed url="" %} ### Related Resources * [PageFly Manual | Guides and tutorials to best use PageFly](https://help.pagefly.io/) * [Browser requirements](https://help.pagefly.io/manual/browser-requirements/) --- # 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.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.