> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/orders-and-transactions/order-statuses.md). # Order statuses Every order in Surge shows one of six statuses: **Submitted, Open, Filled, Cancelled, Dropped, Unknown**. "Open" is normal for 1–2 minutes; after 3 minutes it is flagged as **stuck**. ### The statuses | Status | What it means | Typical duration | Your funds | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- | -------------------------------------------------------------- | | **Submitted** | Surge broadcast your signed transaction; it has not yet appeared in a block | Under a minute | Committed; the transaction is in the mempool | | **Open** | The transaction is in a block. Your order is sitting at the DEX waiting for the batcher | 1–2 minutes normally | Locked in the order at the DEX | | **Filled** | The batcher executed the order and paid your wallet | Final | Proceeds in your wallet (the payout address), deposit returned | | **Cancelled** | The order was returned without executing — either the DEX refunded it (Minswap, when the price moved past your minimum) or you cancelled it | Final | Back in the funding wallet, minus network fees | | **Dropped** | The transaction never got into a block; the network discarded it | Final | Never left your wallet | | **Unknown** | Surge could not find the order inside the transaction, so it cannot track the fill automatically | Until you check | Check the transaction on Cardanoscan | There is no separate "Refunded" status: a DEX refund and a user cancel look the same on chain and both show as Cancelled. ### Stuck orders An **Open** order older than **3 minutes** is labelled stuck. The Recent activity table and the wallet detail page then show a **diagnosis**: | Diagnosis | Meaning | What to do | | ------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------ | | Waiting for the batcher | Under 3 minutes; normal | Wait | | Fillable — batcher running late | The pool would still pay at least your minimum; the batcher just hasn't got to it | Wait a little longer | | Won't fill | The pool now pays less than your minimum (the shortfall is shown in basis points) | Cancel and reclaim, or wait for the price to come back | | Unknown | Surge has no minimum on record for this order (manual swaps), or no pool snapshot | Check the price; cancel if it has clearly moved | The precise "fillable / won't fill" diagnosis is available for strategy orders that recorded their minimum; plain manual swaps get "waiting" then "unknown". ### Strategy-level steps Strategy pages show finer, strategy-specific steps layered on top of these statuses: * **Grid rungs:** armed → pending build → pending sign → submitted → (filled → re-armed) / cancelling. * **Rule levels:** armed → pending build → pending sign → submitted → armed or spent; failed; disabled. * **Arbitrage opportunities:** detected → buying → selling → completed; executing (parallel); partial; abandoned. * **Cadence orders:** pending → awaiting signature → submitted → completed / skipped / failed. Each is explained on the strategy's page. ### Transaction confirmation and order fill These are different. "In a block" (Submitted → Open) says your *order was placed*. "Filled" says the batcher *executed* it. An order can be confirmed on chain and never fill. The transaction status feed pushes "status updated" toasts as your transaction is seen in a block and then finalised; the fill status comes separately from watching the chain for the batcher's transaction. See [Fills and refunds](/orders-and-transactions/fills-and-refunds.md). ### Where statuses appear * **Dashboard → Recent activity** and the **Activity** page: every order with status, diagnosis and a "Cancel & reclaim" action when applicable. * **Strategy trade logs**: the strategy's own orders. * **Wallet detail page**: orders placed from that wallet, plus a Recover Stuck Order dialog. * **Order status pushes**: arbitrage strategies push live order status changes to the dashboard without a reload. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.surgecardano.com/orders-and-transactions/order-statuses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.