> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/analytics-and-reports/fix-an-a-b-test-xlsx-export-error.md). # Fix an A/B Test XLSX Export Error Explains how to fix an XLSX export error caused by special characters in an A/B test's name. Use this guide to fix an error that occurs when downloading an XLSX export from a running A/B test so you can access your test results without interruption. #### What causes this error If you see an error page when trying to export A/B test results as an XLSX file, the most likely cause is a special character in the test name — for example `+`, `&`, or `%`. Special characters in the test name interfere with the export download. This is a known product limitation. Renaming the test to remove the special character resolves the issue immediately. #### How to fix it 1. Go to **Popups** and open the **A/B Tests** tab 2. Open the affected test 3. Rename the test to remove any special characters. For example, replace `Summer + Fall` with `Summer and Fall` 4. Click **Save** 5. Retry the **XLSX export** — the file should now download successfully #### Notes and best practices * **Avoid:** Using special characters such as `+`, `&`, or `%` in A/B test names. These can cause export errors * **Recommended:** Use plain words or hyphens instead (e.g., `Summer and Fall`, `Summer-Fall`) If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help! --- # 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.recart.com/analytics-and-reports/fix-an-a-b-test-xlsx-export-error.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.