{"section":"known-issues","requestedLocale":"en","requestedSlug":"transaction-cancellation-error-with-unreachable-code-message","locale":"en","slug":"transaction-cancellation-error-with-unreachable-code-message","path":"docs/en/known-issues/Payments/transaction-cancellation-error-with-unreachable-code-message.md","branch":"main","content":"## Summary\n\n\nTransaction cancellation requests may fail with the message “Unreachable code” (visible only via API) when a cancellation is sent to the Payments gateway.\n\nThe error can occur in different cancellation flows, full or partial, and may happen before transaction capture, regardless of whether a payment split has already been created.\n\nScenario 1 – Full transaction cancellation (Payments API)\n\nA full transaction cancellation can fail returning the message `Unreachable code` (only visible via API).\n\nThis error happens in payment split scenario, in the UI you can see the cancellation attempt logs but no response.\n\nScenario 2 – Partial cancellation triggered by OMS (before capture)\n\nA partial cancellation initiated by OMS (for example, during a change order) may fail with “Unreachable code”, even before the transaction is captured.\n\nAt the moment of the error:\n\nThe transaction is not captured;\n\nNo payment split exists yet.\n\n\n#### Simulation\n\n\nWe were not able to simulate this error.\n\n\n#### Workaround\n\n\nScenario 1\nCancel the payments separately, starting with the lowest value.\n\nScenario 2\nOpen a ticket with the Product/Payments team requesting the transaction to be finalized (captured).\nOnce the transaction is finalized, proceed with a refund for the required amount."}