Cancelling stuck orders

A stuck order is one still Open more than 3 minutes after placement. On Minswap it will refund itself if it cannot fill; on SundaeSwap, WingRiders and Splash it stays open until you cancel it. Cancelling means signing a transaction that takes your own order back out of the DEX and returns the funds to your wallet, minus one network fee.

Per-DEX behaviour

DEX	If the order cannot fill	You need to cancel?	Special requirements
Minswap	Refunded automatically to the funding wallet	Usually not; you can still cancel while it is open	—
SundaeSwap	Parks indefinitely	Yes	—
WingRiders	Parks; the order also expires 20 minutes after placement, but expiry does not return funds by itself	Yes	—
Splash	Parks indefinitely	Yes	The signing wallet must hold a plain-ADA coin of at least 5 ADA to serve as collateral

"Parks" means the funds are locked in the order on chain. Only the wallet named as the order's owner can cancel it; nobody else, including Surge, can move them.

Where to cancel

• Strategies (grid, rule-based, arbitrage): after an order has been open for 5 minutes on a non-refunding DEX, Surge builds the cancel for you and pushes a Cancel ready prompt to the strategy page (and, for arbitrage, an "opportunity update" with the cancel attached). Approve it and the funds return; the strategy re-arms. Arbitrage also re-offers cancels for any parked leg for up to 6 hours after the opportunity ended.

• Manual swaps and any order: Dashboard → Recent activity, or the Activity page, or the wallet detail page → Recover stuck order. The dialog shows the diagnosis (minimum to fill, what the pool pays now, the shortfall) and a Cancel & reclaim funds button. It first checks on chain whether the order is still open.

• Cadence: cancel from the strategy's trade log row.

What happens when you cancel

1. Surge locates the order on chain and reads its owner from the order's datum. It tries your connected wallet and your strategy wallets as candidates; the one whose key matches the datum (payment or stake key) is the signer. Wallets that share a stake key with the funding address are accepted, because wallets hand out many receive addresses.

2. Surge builds the reclaim transaction and, for the matching wallet, either your extension prompts (browser wallet) or the transaction guard checks it (strategy wallet — cap: locked value plus 10 ADA).

3. You sign; Surge broadcasts; a "cancel" entry is added to your history.

4. The cancel spends the order, so the fill watcher sees it and marks the order Cancelled. This takes a block or two; the status does not change instantly.

When cancelling fails

Message	Cause	What to do
Order not found / may already be cancelled or executed	The order output has already been spent — it filled or was refunded while you were looking	Refresh; check the trade log
Bad inputs (chain rejected)	Same race: the batcher filled it between build and submit	Nothing — you were filled
Not owned	None of your wallets matches the order's owner	The order was placed by a wallet whose key is not in this browser (reconnect it from its key file), or it is not your order
Unsupported DEX	The DEX cannot be cancelled through Surge	—
Collateral required (Splash)	No plain-ADA coin ≥ 5 ADA in the wallet	Send 5 ADA to the wallet as a separate transfer, then retry
Lookup unavailable	The chain lookup timed out	Retry in a moment

After 24 hours

Surge stops watching an order that no batcher has touched for 24 hours. It is still open on chain and still cancellable from the wallet detail page; its status in Surge just will not update on its own once cancelled. [VERIFY: whether a cancel after the 24-hour cutoff is reflected in the trade log.]

Avoid parked orders

• Prefer Minswap for one-off swaps if you are not going to watch them.

• Use a slippage tolerance that reflects how fast the token moves; a tight tolerance on a volatile token parks more often.

• Keep your tab open while strategy orders are out, so Cancel ready prompts can reach you.