> 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/only-some-products-updated.md). # Why were only some products updated? The task finished as Partially complete or updated fewer products than expected. ## The plan limit was reached Each plan allows a maximum number of products per task (for example 100 on Free). When a task matches more, the first products are updated and the task ends as **Partially complete** with the message *This task matched N products, but only the first M were processed under your current plan*. Upgrade on the **Pricing** page and choose **Continue change** on the task to process the rest. See [Plans and pricing](/bulk-price-editor-sami/settings-and-plans/plans-and-pricing.md). ## Products changed while the task ran If products were deleted or edited in Shopify between the export and the write, the task cannot update them and lists them in the error banner. Click **Export list** for the full list. See [Task errors and warnings](/bulk-price-editor-sami/manage-tasks/errors.md). ## Variant rules or exclusions Products that are excluded, or whose variants do not match your **Apply to variants** conditions, are shown greyed out in **Product changes** and are counted as not changed. That is expected. ## Automated collections Collection membership in the task is read when the task starts. Products added to an automated collection after that moment are not included. Create a new task, or duplicate the finished one, to catch them. ## The edit produced no change Rows whose new value equals the old value, or whose text edit would have produced an empty result, are left unchanged. --- # 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/only-some-products-updated.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.