# How to debug :point\_right: Try creating NOVs, put option variables there, one by one, and check ajax request-response on the front-end. Also test your NOVs this way. :point\_right: Another way of debugging is this one: drag and drop a new option of the same type that you are going test. For instance, if it is Text input, then create a new Text Input. Then open its settings and choose 'duplicate', then choose targeted option in the dropdown and click 'submit'. This action fetches current settings for the targeted option from DB, so you can compare what actually is in DB with what you think there is (based on what you see in the current product). For instance, your Select option can have suboptions 'green' and 'yellow' in the current instance, but in reality it is already overwritten from another product and has suboptions 'red' and 'white'. And this is why your price calculation fails - the data is different! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kb.moomoo.agency/uni-cpo-4-documentation/how-to-debug.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.