{"section":"known-issues","requestedLocale":"en","requestedSlug":"specification-update-through-api-or-webservice-doesnt-send-product-for-indexing","locale":"en","slug":"specification-update-through-api-or-webservice-doesnt-send-product-for-indexing","path":"docs/en/known-issues/Marketing & Merchandising/specification-update-through-api-or-webservice-doesnt-send-product-for-indexing.md","branch":"main","content":"## Summary\n\nThe product specification update through API or webservice should send the item to the indexing queue, to be updated on the site and in the search APIs. However, this is not happening as expected. That is, the product is not being sent for indexing.\n\n\n## Simulation\n\n1. Update the value of a product field (specification) through API or webservice. See the [API documentation](https://developers.vtex.com/vtex-rest-api/reference/updateproductspecificacatalog-api-post-update-product-specificationtion)\n2. With the `200 (OK)` return, note in the administrative panel that the value has in fact been changed.\n3. Note, however, that in the following instants the product will not enter the indexing queue.\n\n## Workaround\n\nSince this case can impact catalog integrations, we suggest that, until we correct this behavior, after the update of a specification, the middleware algorithm performs an update on the product, with the sole goal of placing it in the indexing queue."}