{"section":"known-issues","requestedLocale":"en","requestedSlug":"inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace","locale":"en","slug":"inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace","path":"docs/en/known-issues/Logistics/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md","branch":"main","content":"## Summary\n\n\n\nThere is a flow in case of accounts VTEX using External Maketplaces and that account should notify this external Marketplace regarding SKU inventory update. And due cache or full queue that syncronous information does not go ahead correctly.\nNowadays in the ItemAvailability flow, if there is an error to save into the elasticsearch, a worker will save it instead. If fore some reason the queue is full and an item takes more time to be persisted into the elasticsearch, the information in the cache can become inconsistent.\n\n\n\n\n## Simulation\n\n\n\nThere is no way to simulate the error, but you will see the incorrect update to the integration side with the previous value of inventory.\n\n\n\n\n## Workaround\n\n\n\nThere is no workaround available."}