{"section":"known-issues","requestedLocale":"en","requestedSlug":"error-with-event-system-at-the-end-of-a-transaction-causes-an-order-to-be-incomplete","locale":"en","slug":"error-with-event-system-at-the-end-of-a-transaction-causes-an-order-to-be-incomplete","path":"docs/en/known-issues/Order Management/error-with-event-system-at-the-end-of-a-transaction-causes-an-order-to-be-incomplete.md","branch":"main","content":"## Summary\n\n\nWhen an error occurs with the event system at the end of a transaction, the order that the customer was trying to buy is not finalized and remains incomplete. The \"RaiseEvent\" action is an internal action triggered in the last steps of the order creation, always after the transaction/payment being done (not necessarily approved or analyzed; they can have their own flows and timings), when an error occurs in this step, being it at the end of a purchase, for example GatewayCallback, the user cannot complete his purchase, thus canceling the transaction due to the failure of this event.\n\n\n#### Simulation\n\n\nThere's no way to simulate, but we can see the logs:\n\nRaiseEventyAsync failed in the last 30 days counted by workflow type\n\nRaiseEventAsync & RaiseEventAsyncV2 in the workflow_type PlaceOrder & NewGatewayCallback\n\n\n#### Workaround\n\n\nN/A"}