> 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/multiple-tasks-same-time.md). # What happens if multiple bulk edit tasks start at the same time? What happens when several tasks are scheduled for the same moment or overlap on the same products. ## They are processed one after another The app sends every change to Shopify as a bulk operation, and Shopify runs **one bulk operation per store at a time**. When several tasks start together, each waits for the previous one to finish its step, so the work is effectively queued. A task can therefore sit in **Pending execution** or **Running** for a while before its own products change. ## Overlapping products: last write wins Each task calculates its new values from the product data it reads when it starts and then writes them. If two tasks change the same field on the same products, the one that writes last decides the final value. The second task's "original" value is whatever the first task had already written, so reverting the tasks in the wrong order can leave unexpected values. **Recommendations** * Do not run two tasks on the same field and the same products at the same time. Schedule them at least a few minutes apart, or combine the change into one task. * Revert tasks in the reverse order of how they ran. * Avoid manual product edits while a task is **Running** or **Revert in progress**. ## Recurring tasks Several recurring conditions in one task must not overlap, and the app enforces that in the form. Two separate recurring tasks on the same products are not checked; treat them like any two overlapping tasks. --- # 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/multiple-tasks-same-time.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.