> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api-references/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes/error-format-for-admin-apis/warning-objects.md). # Warning objects Understand warning error objects. Warning objects are alerts generated during the [deployment process](https://docs.digitalriver.com/commerce-api/admin-apis/product-management/manage-products-asynchronous-api/deploying-a-product) that indicate potential issues with the product setup. While they do not prevent the deployment of a product, they flag areas that could lead to suboptimal performance or presentation in your store. Addressing these warnings before deployment is highly recommended to ensure the product functions and appears as intended. ## Deployment error A deployment error indicates a major setup issue with the product, likely affecting its sale and fulfillment in your store. You cannot deploy products with deployment errors until you fix all errors. It prevents you from deploying a product that will fail to sell correctly in your store. ## Deployment warning Deployment warnings identify potential issues with your product's setup [during deployment](https://docs.digitalriver.com/commerce-api/admin-apis/product-management/manage-products-asynchronous-api/deploying-a-product). They highlight concerns that might affect the product's performance or appearance in your store but do not prevent it from being deployed. It is advisable to address these warnings before proceeding with deployment to ensure optimal functionality and presentation of your product. ## Live change warnings Live change warnings appear when you apply [live changes to a base product or product variation through programmatic means](https://docs.digitalriver.com/commerce-api/admin-apis/product-management/manage-products-asynchronous-api/applying-live-changes#applying-a-live-change-to-a-base-or-individual-product). These warnings indicate potential issues with the changes you are trying to make, such as compatibility problems, errors in the update logic, or conflicts with the current product setup. While these warnings do not prevent the application of changes, they serve as crucial alerts, advising you to review and potentially revise the changes to avoid adverse effects on the product's functionality and availability in your store. --- # 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.digitalriver.com/commerce-api-references/warnings-and-error-codes/error-codes/error-format-for-admin-apis/warning-objects.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.