{"section":"known-issues","requestedLocale":"en","requestedSlug":"activateifpossible-overwritten-by-new-catalog-ui","locale":"en","slug":"activateifpossible-overwritten-by-new-catalog-ui","path":"docs/en/known-issues/Catalog/activateifpossible-overwritten-by-new-catalog-ui.md","branch":"main","content":"## Summary\n\nCurrently, if an sku is switched to ActivateIfPossible = true directly via API and then a change is performed via catalog UI in the same sku while it still didn't have all the necessary requirements to be active, the fieldis switched back to = false.\n\nThe correct bevahiour would be for it to remain = true and only the active value to be switched.\n\n## Simulation\n\n1 - create an sku\n2 - in it, change the activateIfPossible field to true\n3 - access the UI and change any values without filling in all necessary fields for it to be active\n4 - fetch the SKU data again https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/stockkeepingunit/-skuId- and the activateIfPossible field will be = false\n\n## Workaround\n\n-"}