> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/faq/writebackextreme-6.0-rollback-guidance.md). # WriteBackExtreme 6.0 Rollback Guidance In rare cases, specific environments may experience unexpected behaviour after upgrading to **WriteBackExtreme 6.0**. If you observe issues impacting production workflows, we recommend **temporarily reverting to WriteBackExtreme 5.7.4**, which remains stable and fully supported. This rollback is a precautionary measure to keep normal operations running while we continue refining compatibility improvements introduced in version 6.0. #### When should you consider a rollback? You may consider reverting if you observe: * Errors affecting writeback operations * Unexpected data refresh behaviour * Schema / query inconsistencies * Environment-specific instability after upgrade Our development team is actively investigating reported scenarios. If you require assistance, please contact support. *** ### Video example of a downgrade {% embed url="" %} ### Will reverting WriteBackExtreme affect my data? This depends on the **repository database configured during installation**. WriteBackExtreme stores its internal data (including schemas, configurations, audit records, etc.) in the repository database selected when the product was installed. #### How can I confirm which repository database I am using? To verify this, review your **installer configuration / installation settings**: * Check the database type chosen during installation (MySQL / SQLite / etc.) * Your IT / system administrator can typically confirm this quickly *** #### MySQL environments If your repository database uses **MySQL**, WriteBackExtreme data is stored externally on your database server. Reinstalling or reverting versions will **not affect your stored data**, provided the MySQL database itself remains unchanged. As a best practice: * Maintain regular database backups * Verify database availability before rollback *** #### SQLite environments If your repository database uses **SQLite**, WriteBackExtreme data is stored locally on disk. The SQLite database file is located inside the WriteBackExtreme runtime folder: ``` .wbe-runtime ``` When reverting or reinstalling: * Ensure the SQLite database file remains present * If the file is missing, WriteBackExtreme may initialise a new empty database As a best practice: * Back up the SQLite file regularly * Treat it like any other critical data file ### Recommended best practice before rollback Before reverting versions, we recommend: * Confirming your repository database type * Ensuring backups are available * Verifying database/file availability --- # 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.infotopics.com/writebackextreme/troubleshooting-and-faq/faq/writebackextreme-6.0-rollback-guidance.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.