{"section":"known-issues","requestedLocale":"en","requestedSlug":"possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway","locale":"en","slug":"possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway","path":"docs/en/known-issues/Order Management/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md","branch":"main","content":"## Summary\n\n_**Important**: We suggest using the new **Change V2** since the effort went into creating this new feature._\n\nSome problems were identified in the Change Orders V1 architecture, where some cases were not notified in the order interaction in the UI, and were not notified in the Get Orders API, however, there was a discount or increase in the value. We have also seen scenarios where the notification occurs in the UI and API, however, the discount or increase is not made at the gateway.\n\nWe have a second point, which is when the change is inserted via MKP and the seller is whitelabel, in these cases, the change may not be replicated on the Seller!\nThe correct thing to do is to make the change via the seller!\n\n## Simulation\n\nIt is not possible to carry out a simulation, as the scenarios are sporadic and generally occur due to a timeout error, for which we have already increased the timer.\n\n## Workaround\n\nInitially, we do not have a workaround."}