> 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/how-long-does-a-task-take.md). # How long does it take to complete a bulk edit task? How the app processes products and what affects the duration of a task. Most tasks finish within a few minutes. The time depends on: * **How many products and variants match.** The app first asks Shopify to export the matching products, then sends the changes back in batches (400 products per batch for most fields, smaller batches for descriptions and deletions). Each batch is a Shopify bulk operation. * **Shopify's queue.** Shopify runs one bulk operation per store at a time, so a task waits for any bulk operation already running, including other tasks in this app. * **The field.** Descriptions carry more data per product than prices, so they take longer. The task details page refreshes automatically every 10 seconds while the task runs and shows **Products changed** as a progress bar. You can leave the page; the task keeps running. ## Tips * Split very large catalogs into several tasks (by collection or vendor) so each finishes sooner and problems are easier to locate. * Do not start several large tasks at the same moment; they will queue behind each other. * Scheduled one-time tasks start at the scheduled minute. Recurring occurrences are checked every 10 minutes, so they may start up to about 10 minutes late. --- # 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/how-long-does-a-task-take.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.