> 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.md). # FAQs - [Why was the task completed but no changes were made to the product?](https://docs.samita.io/bulk-price-editor-sami/faqs/task-completed-but-no-changes.md): The task shows Completed but the products look unchanged. Here are the usual reasons. - [Why don't changes appear on my storefront immediately?](https://docs.samita.io/bulk-price-editor-sami/faqs/changes-not-on-storefront.md): The task completed and the admin shows the new values, but the online store still shows the old ones. - [Why do my manual edits keep reverting?](https://docs.samita.io/bulk-price-editor-sami/faqs/manual-edits-keep-reverting.md): You changed a product by hand and the app changed it back. - [What happens if multiple bulk edit tasks start at the same time?](https://docs.samita.io/bulk-price-editor-sami/faqs/multiple-tasks-same-time.md): What happens when several tasks are scheduled for the same moment or overlap on the same products. - [How long does it take to complete a bulk edit task?](https://docs.samita.io/bulk-price-editor-sami/faqs/how-long-does-a-task-take.md): How the app processes products and what affects the duration of a task. - [Why is my task stuck in Pending or Scheduled?](https://docs.samita.io/bulk-price-editor-sami/faqs/task-stuck-pending-or-scheduled.md): A task shows Pending execution or Scheduled and does not seem to start. - [Why were only some products updated?](https://docs.samita.io/bulk-price-editor-sami/faqs/only-some-products-updated.md): The task finished as Partially complete or updated fewer products than expected. --- # 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.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.