{"section":"known-issues","requestedLocale":"en","requestedSlug":"transactions-remain-stuck-in-authorized-despite-connector-approval","locale":"en","slug":"transactions-remain-stuck-in-authorized-despite-connector-approval","path":"docs/en/known-issues/Payments/transactions-remain-stuck-in-authorized-despite-connector-approval.md","branch":"main","content":"## Summary\n\nIn some cases, the Transaction Worker fails to advance the transaction to the expected status, even after receiving a successful response (200 OK) from the connector. As a result, transactions may remain stuck in _Authorized,_ and the corresponding orders stay in _\"Payment Pending\"_. This behavior can occur when the connector correctly returns an approved response, but the internal process that updates the transaction status does not execute properly.\n\nThis issue corresponds to scenario: _\"Silence after Authorized\"_, where five distinct root causes were identified sharing the same surface symptom but different failure mechanisms. The other causes are:\n\n- ClearSale antifraud retry loop due to `NullReferenceException` in the connector. Ticket #1059028\n- ClearSale antifraud retry loop due to `address.number=null` . Ticket #496298\n- Payment stuck in `Received` status post-authorization, without visible status in the UI. Ticket #1411012.\n- Status regression `Approved` → `Authorized` caused by a secondary connector callback, resolved together with this KI.\n\n## Simulation\n\nIt is not possible to simulate.\n\n## Workaround\n\nOpen a ticket for Product support team."}