{"section":"known-issues","requestedLocale":"en","requestedSlug":"order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification","locale":"en","slug":"order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification","path":"docs/en/known-issues/Order Management/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md","branch":"main","content":"## Summary\n\n\n\nWhen an order is in the \"Payment Pending\" status, a payment notification is expected to be registered to the Orders module. During this stage, issues in event processing may occur.\nThe OMS is notified through a callback endpoint triggered when the Gateway receives a postback message. This message is generated whenever a transaction reaches specific states (such as _Approved_) and is then processed by a worker who instructs the Gateway to call the callback endpoint, updating the OMS about the new transaction state.\nIn these cases, the postback is sent successfully, the OMS receives it and responds with success, but the order remains stuck due to an unlogged error in the OMS.\nIn other words, the Gateway completes its role correctly, while some error in the OMS processing prevents the order from progressing.\n\n\n#### Simulation\n\n\n\nThere's no way to simulate this behavior.\n\n\n#### Workaround\n\n\n\nPlease contact our support team so they can use the internal troubleshooter tool"}