> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/faqs/manual-edits-keep-reverting.md). # Why do my manual edits keep reverting? You changed a product by hand and the app changed it back. ## A scheduled revert ran When a task has **Schedule the revert** set, the app restores the values the products had **before the task**, at the scheduled time. It does not check whether someone edited the product in between. *Example:* 10:00 the task changes a price from 50 to 60. 10:30 you manually change it to 55. 11:00 the scheduled revert runs and sets the price back to 50. Your 55 is lost. **Fix:** before editing products by hand, open the task and use **Cancel revert schedule**, or move the revert with **Reschedule revert**. See [Revert changes](/bulk-price-editor-sami/manage-tasks/revert-changes.md). ## Someone pressed Revert now **Revert now** does the same thing on demand. Check the **Revert status** card of recent tasks for a **Reverted on** date. ## A recurring task is active A recurring task applies its change at the start of every occurrence and reverts at the end, for example every day at 06:00 and 18:00. Manual edits to the same field are overwritten twice a day. Open **Tasks**, look for **Daily**, **Weekly** or **Monthly** in the **Recurring** column, and use **Cancel recurring task** or **Finish recurring** if you no longer want it. See [Recurring tasks](/bulk-price-editor-sami/manage-tasks/recurring-tasks.md). ## How to avoid it * Finish manual edits before creating a task, or make them after the task has been reverted. * Use the task's **Note** to tell your team that a revert is scheduled. * Enable [email notifications](/bulk-price-editor-sami/settings-and-plans/notifications.md) so you know when a task runs or reverts. --- # 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.samita.io/bulk-price-editor-sami/faqs/manual-edits-keep-reverting.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.