Managing orders
Follow your orders in the Orders widget and the order sheet, amend or cancel them, get notified when they finish, and read why an order ended.
The Orders widget lists your orders, and the order sheet shows everything about one of them. This page covers both, how to amend and cancel an order, the notifications and the bell that tell you an order finished, what an unconfirmed order means, and the reasons an order ends. How each algo works is on its own page: DMA, Chase, TWAP, Sniper and Spreader.
The Orders widget
The widget has two tabs, Open Orders, with a count, and Order History. In a narrow panel the tabs read Orders and History. Both list the orders of the account selected in the terminal.
Click a row to open its order sheet. Click a column header to sort by it, and drag a header to move the column. Aura keeps your sort, column order and widths. Columns appear as the panel gets wider.
The right-click menu
Right-click an order, in either tab, for its menu:
| Item | What it does |
|---|---|
| View details | Opens the order sheet, as clicking the row does. |
| Copy to ticket | Fills the order ticket with the order. See below. |
| Amend order | Open Orders only, for an algo you can amend: opens the order sheet with the amend form open, as the pencil does. |
| Cancel order | Open Orders only: cancels the order, as the ✕ does. It is greyed while a cancel is already on its way. |
| Copy order ID | Copies the order's full ID. |
Copy to ticket fills the order ticket with the order's market, algo, side, quantity, limit price and the algo's settings. If the order is on another market, the ticket switches to that market first. The start and expiry are not copied: the copy starts now and stays open until it fills or you cancel it. Nothing is sent until you check the ticket and press its button.
Open Orders
| Column | What it shows |
|---|---|
| Time | When the order last changed. The header names the time zone. |
| Pair | The market. |
| Side | Buy or Sell. |
| Order | The algo. Hover it for the order ID. |
| Price | The order's limit price. |
| Avg fill | The average price of the fills so far. |
| Amount | The order's size and its currency, such as 0.5 BTC or 1,000 USDT. |
| Outstanding | The unfilled size of the child orders the order has at the exchange, in the base asset. It is not what is left of the whole order, part of which may not be at the exchange yet. For a spreader it counts the lead leg only. |
| Filled | A bar and the share of the order filled. |
| Notional | The value filled so far, in the quote currency. |
| Fee | The fees paid so far, in the quote currency. A spreader's counts both legs when they share a quote coin, and shows — while a leg's fee isn't known yet. |
| Live | How many child orders are working at the exchange. |
| Status | The order's status. See Order statuses. |
Hover a row to show two buttons at its end. The pencil (Amend order) opens the order sheet ready to amend. The ✕ (Cancel order) cancels the order. The pencil shows only for an algo you can amend, so a DMA order has none.
Cancel All, above the table, sends a cancel for every order in the list that can be cancelled. It asks for no confirmation. It is hidden in a narrow panel.
Order History
Order History has the same columns as Open Orders, with three differences:
- Created replaces Time and shows when you placed the order.
- There is no Outstanding, Live, or button column.
- A red +X over chip beside the status means the order filled past its size.
Once Aura has scored your finished orders, two more columns appear in the widest layout: Participation and Maker %. Execution cost explains them.
History loads one page at a time. Older orders load as you scroll down.
Order statuses
While an order is open, its status says what it is doing. Hover new, working, armed, waiting, pacing or past end for a short explanation.
| Status | Color | Meaning |
|---|---|---|
| new | Grey | Accepted, not working yet. |
| working | Cyan | A child order is working at the exchange. |
| armed | Cyan | A Sniper, or a Spreader with a Take lead, waiting for the price or the spread to reach its limit. |
| waiting | Amber | Waiting for market data. |
| pacing | Amber | A TWAP waiting for its next slice. |
| past end | Amber | Working past its end time. |
| scheduled | Amber | Waiting for its start time. |
| amending | Amber | Aura is applying your change. |
| cancelling | Amber | Aura is cancelling the order at the exchange. |
| expiring | Amber | The order reached its expiry, and Aura is cancelling what is left. |
| unconfirmed | Amber, with an hourglass | The exchange hasn't answered a request. See Unconfirmed orders. |
A finished order shows how it ended.
| Status | Color | Meaning |
|---|---|---|
| filled | Green | The order filled. |
| cancelled | Grey | The order ended with nothing filled. |
| part. cancelled | Amber | The order ended after a partial fill. |
| rejected | Red | A DMA order the exchange rejected, an order above your Max USD notional, or an order that never reached the exchange because the account had no connection. Other algos the exchange rejects end cancelled or part. cancelled, with the reason in the order sheet. |
| not created | Red | Aura never created the order. |
| not confirmed | Amber | Aura could not confirm that the order was created. |
A warning triangle on the status means the order needs attention. See Needs attention.
The order sheet
The order sheet opens when you click an order. It shows the order's figures, its settings, and every child order and fill.
The header
The header names the pair, the algo, the side and the status. Chips beside the status flag what needs a look:
- ⚠ needs attention: see Needs attention.
- Unconfirmed since a time: hover it to see for how long.
- Overfilled by an amount: the order filled past its size.
Under it you see the exchange, the account, when the order was Created and last Updated, and the order ID. Click the ID to copy it.
The header has two buttons:
- Amend turns the Order column into fields, where it stands. It stays pressed while you amend, and pressing it again leaves without sending anything. While an earlier change is still being applied, it is disabled and reads "Waiting for the last change to apply" on hover.
- Cancel Order cancels the order and closes the sheet.
Notices
Boxes under the header explain anything out of the ordinary:
| Box | When it shows |
|---|---|
| Red, with a reason | The order ended for a reason other than a fill or a cancel by you or Aura. See Why an order ended. |
| Amber, one per child order | The exchange hasn't confirmed a child order or its cancel. See Unconfirmed orders. |
| Amber, Needs attention | Something stopped Aura from managing the order normally. |
| Red, an overfill | The order filled past its size. |
| Red, an API key problem | The order is being cancelled or changed, but Aura can't use the account's API key. Its child orders stay at the exchange and can fill. The box says to update the key or cancel on the exchange's site. |
Summary figures
| Figure | What it shows |
|---|---|
| Filled | The amount filled, and the share of the order's size. |
| Avg fill | The average fill price. Below it, Arrival mid is the mid price when the order arrived. Hover a rounded figure for its exact value. |
| Notional | The value filled. Once the order has finished, the line below says how long it worked. An order sized in the quote currency shows Size instead: the amount of the asset it bought or sold. |
| Fees | The fees paid, with the fees in bps and the share filled as maker. |
A spreader shows Realized spread in place of Notional, with its spread limit below it.
Two rows sit under the figures for some algos:
- A TWAP shows a Progress row: a bar of what has filled against where the schedule says it should be, and lines such as "Behind schedule by", the current slice, and what happens at the end. See TWAP.
- A spreader shows a Legs row: a bar for each leg and how much of the lead is unhedged. See Spreader.
Execution, TCA and Order
Under the figures, three columns sit side by side, or one under the other in a narrow sheet. Each is a list of rows.
| Column | What it shows |
|---|---|
| Execution | Outstanding (the unfilled size of its child orders at the exchange) and Working children while the order is open, Arrival bid / ask and Arrival spread (or Arrival book: Not captured when there was none), and the maker and taker split, over both legs for a spreader. A spreader also shows its executed size and notional and its Hedge market. |
| TCA | The order's cost against its arrival book: live figures while it works, the full report once it finishes. A spreader's appears once it has finished. See Execution cost. |
| Order | Quantity and the algo's settings. Reduce only shows on perpetuals. Starts or Started shows once the order has a start time. Expires always shows, and reads No expiry for an order without one. |
On an open Chase, TWAP or Sniper with a limit price, the limit line also shows how far the market is from your limit, such as "Bid 7.2 bps above". It turns amber once the market is past your limit.
Children, Fills and Amendments
Three tabs at the bottom of the sheet list the order's records, each with a count.
| Tab | Columns |
|---|---|
| Children | Time, Type (IOC, Post or Post only), Price, Qty, Filled, Status, Internal, External, First fill and Venue order ID. |
| Fills | Time, Price, Qty, Fee and Liq. (Maker or Taker). |
| Amendments | Applied, Field, Old and New. The fields of one amend share one time. |
A spreader's Children and Fills also show a Leg column. Once a finished order is scored, a strip above the tables gives the medians for Internal, External and First fill. Execution cost says what each measures. Long lists load in pages with Load more.
How times are shown
Times show in the time zone you pick under Settings, Time zone: your local zone or UTC. A column names the zone once, in its header. A single time names its zone beside it. A date shows its year only when it isn't the current year. See Settings.
How figures are shown
Prices show at the market's tick and amounts at its size step. Hover a figure for its exact value when it shows fewer digits. See How figures are shown.
Amending an order
Press Amend in the order sheet, or the pencil in Open Orders. The Order column becomes the amend form where it stands: every setting keeps its row, the ones you can change turn into fields, and the rest are dimmed. A setting the order was placed without, such as a limit price, gets a row of its own so you can add it. Nothing else on the sheet moves.
| Algo | What you can change |
|---|---|
| DMA | Nothing. Cancel it and place a new order. |
| Chase | Quantity, Chase distance, Post only, Reduce only, Limit price, Expires, Starts |
| TWAP | The Chase fields, plus Duration, Interval and At end |
| Sniper | Quantity, Reduce only, Limit price, Expires, Starts |
| Spreader | Quantity, Max spread or Min spread, Lead ahead cap, Limit price, Expires, Starts |
The side, the market and the account never change.
A field you change shows a teal dot, and its old value beside the label, such as "was 5 bps". Discard and Apply sit on the column's title line, which reads No changes yet until you change something. Press Apply (it reads Apply 2 changes with two edits) to send them all as one amendment, or Discard to drop them. A toast reads "Amend requested." once Aura has your change.
Rules
- Quantity is the new total size, not an addition. It must be more than what has already filled. A quantity in the coin you trade, or in USD on an inverse perpetual, follows the ticket's size checks: a whole number of the exchange's lot size and at least its minimum size. Except on a Spreader, it must also leave at least that minimum still to fill. The box says what's wrong, for example Must be a multiple of 0.001 BTC or Leaves less than the 0.01 BTC minimum to fill.
- Duration on a TWAP counts from the schedule's start. Its label is a menu: pick Total from start to enter the whole duration, or Time remaining to enter the time left from now. Once you change it, the line under it says when the schedule will end.
- Interval must be at least 1 second and can't be longer than the duration.
- Expires must be a few seconds in the future and at most 365 days away. On a TWAP, it can't come before the schedule ends. No expiry (GTC) removes the expiry.
- Starts can change only while the order is scheduled. Start now starts it at once.
- Limit price can be cleared to remove the limit. On a buy it must be at least one tick: below that the box reads, for example, Minimum 0.1 USDT.
- Reduce only shows only on perpetuals. It applies to child orders placed after the amendment.
- Lead ahead cap can't be more than the Quantity.
What happens when you apply
Aura cancels the order's open child orders, then restarts the order with your new settings under the same order ID. Meanwhile the status reads amending. A scheduled order takes the change at once, since it has no child orders yet.
You can have one amendment in progress per order. If you cancel the order while it is amending, the cancel wins and your change is dropped.
If the order's old Expires time passes while it is amending, the order expires and your change is dropped, unless your change moved Expires later or removed it. Then the change applies and the order keeps working to its new Expires.
Cancelling an order
You can cancel from three places: Cancel Order in the order sheet, the ✕ in Open Orders, or Cancel All for every open order. A toast reads "Cancel requested." once Aura has your cancel.
The order then reads cancelling while Aura cancels its child orders at the exchange. It ends cancelled if nothing filled, or part. cancelled if something did. An order reaching its expiry reads expiring in the same way.
You can cancel an order while it is working or amending. You can't cancel it again while it is cancelling or expiring, because the cancel is already going.
Notifications
A notification appears at the bottom right of the screen when one of your orders:
- Is placed. "Chase placed", or "TWAP scheduled" for an order that starts later, over what the order is for and its limit, such as "Buy 0.5 BTC-USDT · limit 79,800.0". It shows wherever you placed the order: the ticket, a position's Close, another tab or another device.
- Has a child order rejected while it works on. "Chase · child rejected" says the exchange's reason, such as "Insufficient balance", and counts up as more follow: "Chase · child rejected ×3". A price the exchange refuses doesn't count, since the order sends its next price at once. A rejection that ends the order is the order's own.
- Finishes, every way: filled, partially cancelled, cancelled, expired or rejected, a cancel you asked for included. A partial fill doesn't get one.
Each order has one notification, which changes as the order goes: "Chase placed" becomes "Chase · child rejected", then "Chase filled".
When an order finishes, the notification names the algo and how the order ended, such as "Chase filled". Below that it says what traded:
| Line | When |
|---|---|
| "Bought 0.5 BTC-USDT" | The order filled. |
| "Bought 0.2 of 0.5 BTC-USDT" | It ended after a partial fill. |
| "Buy 0.5 BTC-USDT" | Nothing filled. |
The average fill price is under Avg fill, in the Orders widget and on the order's sheet.
A third line gives the reason when the order ended for something other than a fill, your cancel or its expiry, such as "Rejected by the exchange · Insufficient balance". See Why an order ended.
- Colour. The title, its icon and a stripe on the left say what happened: teal when the order is placed, gold when a child order is rejected, green when it filled and red when it was rejected. A cancelled, partially cancelled or expired order's notification stays plain. Other notifications use the same colours: green when something you asked for went through, red when it didn't.
- Every account. You get notifications for all your accounts, not only the one selected in the terminal. An order on another account starts with the account's name, such as "OKX Paper · Sniper filled".
- How long. A notification stays 6 seconds from its last change, and longer while the pointer is on it. A rejected order's stays until you close it.
- Many at once. When more than three orders finish within a second, they fold into one notification, such as "12 orders cancelled", or "5 orders ended" with a count of each kind.
- View opens the order sheet. It shows for an order on the account selected in the terminal while the Orders widget is open.
- While you were away. Nothing that happened while the terminal was closed, or while its connection was down, gets a notification. The bell lists the orders that finished.
- Choosing which. Settings has a switch for each kind: Order placed, Order finished and Child order rejected. All three start on. See Settings.
Notifications make no sound and don't appear outside the browser tab.
The bell
The bell in the top bar lists your latest finished orders across your accounts, whichever notifications you've switched on, newest first, in the words of their notifications, with the time each finished. It lists up to 30.
A number on the bell counts the orders that finished since you last opened it, shown as 9+ past nine. Opening the bell marks them read. Each keeps a dot until you close the bell, so you can see which were new. Click a row to open its order sheet, in the same cases as View.
Aura remembers when you last opened the bell in this browser, so the count survives a reload. The first time you open the terminal in a browser, nothing counts as new.
The bell checks the 50 most recent orders of each account. An older order that finished while the terminal was closed doesn't show in it. Order History still has it.
Unconfirmed orders
An order reads unconfirmed when the exchange hasn't answered a new child order or a cancel for 15 seconds, or at once if the connection dropped while the request was on it. The mark stays until the exchange answers. No timer clears it.
Aura shows the mark in five places:
- The Status column shows the hourglass badge. The hover gives the order's own status, what the exchange hasn't confirmed and since when, and how much may fill.
- The order sheet's header shows Unconfirmed since a time.
- The order sheet shows an amber box for each child order the exchange hasn't confirmed.
- The order sheet's Children tab shows the hourglass in the Status column of each child order the exchange hasn't confirmed.
- The ticket shows a line above its submit button, such as "Kraken hasn't confirmed 2 orders since 12:03:04 UTC (up to 0.9 BTC buy). New orders are still sent."
What the box says
The box names what the exchange hasn't confirmed and why:
| Cause | Meaning |
|---|---|
| no answer | Nothing came back from the exchange. |
| connection lost | The connection dropped while the request was on it. |
| An exchange error, such as Kraken error | The exchange answered with an error that doesn't say whether the request worked. |
Then it says what the child order may be doing. An IOC child may have filled or not been placed, but it can't still be resting. Any other child may be resting, filled, or not placed. The box gives the most that can still fill, which is the child's size less its confirmed fills, and what has been confirmed so far.
What happens next
- A new child order with no answer. The order sends nothing else until the exchange answers. You don't need to do anything. Cancel Order stops it.
- A cancel with no answer. If you cancelled the order, or it is expiring or its schedule has ended, Aura re-sends the cancel every 5 seconds and the order closes when the exchange answers. If Aura was cancelling the child order to move its price, the order posts nothing new until the exchange answers.
- A Coinbase order not yet confirmed. Coinbase cancels an order only by its own order ID, which comes with its confirmation. Until then Aura can't cancel it, and the box says to cancel it on Coinbase's site.
If the exchange has no record of a child order 65 seconds after it was sent, the child reads not placed. A fill that arrives later is still booked.
Cancel Order and the ✕ follow the order's status, never the mark. There is no button to ignore or retry an unconfirmed order: only the exchange can settle it. If you act on the exchange's own site, Aura sees the result when the exchange answers.
Note: Aura never trades back an overfill. If an order fills past its size, the red box tells you how much extra you hold. Trade it back yourself if you don't want it.
Why an order ended
When an order ends for a reason other than a fill or a cancel by you or Aura, the order sheet shows a red box, whatever the order's status. The box gives the reason's title, a category when there is one, and the exchange's own text when it sent one, with the exchange's name in front, such as "OKX: Order failed. Insufficient USDT margin".
| Reason | When it happens |
|---|---|
| Rejected by the exchange | The exchange rejected a child order, and the order could not continue. |
| Refused by the exchange, can't resend | The exchange refused a child order in a way Aura can't retry. |
| Stopped after repeated rejections | Five child orders in a row were rejected with no progress at the exchange. Rejections for the exchange's rate limit don't count: the order waits and sends again. |
| Position already closed | A reduce-only order had no position left to reduce. |
| Cancelled by the exchange for margin | The exchange cancelled a child order for a risk or margin reason. |
| Cancelled by the exchange | The exchange cancelled a child order, such as a post-only or self-trade cancel, and the order could not continue. |
| Order could not be sent | A child order could not be sent from this account. |
| Remainder below the exchange's minimum size | What was left fell below the market's minimum order size. |
| Remainder below the exchange's minimum order value | What was left could not meet the exchange's minimum order value at the current price. |
| Above your Max USD notional | The order's value was above the Max USD notional in your risk settings. See Settings. |
| Exchange account disconnected | The account lost its connection to the exchange for more than 5 seconds, or the exchange refused its API key, before the order reached the exchange. |
| Exchange account could not connect | The account could not connect to the exchange when the order needed it. See Connection status. |
| Closed when the paper account was restored | You reset a paper account whose saved state Aura couldn't restore, and its open orders closed with what they had filled. |
| Amended order was refused | After an amendment cancelled the child orders, the order could not restart with the new settings. |
| Expired | The order reached its Expires time. |
| Not created | Aura never created the order. |
| Creation not confirmed | Aura could not confirm that the order was created. |
A reason with no title of its own reads Order ended.
The category is one of Account restricted, API key refused, Duplicate order ID, Exchange unavailable, Market unavailable, Insufficient balance, Price not accepted, Size not accepted, Request not accepted, Too many open orders, Order already closed, Order not found, Position limit reached, Exchange rate limit or Position already closed.
An order that filled, or that you or Aura cancelled, shows no box. Hover its status to read any detail. A spreader's detail gives its unhedged and hedged amounts and its realized spread. An order sized in the quote currency may end filled with what was left too small for one more order the exchange accepts, and its detail says how much was unspent.
Needs attention
When something stops Aura from managing an order normally, the status shows a warning triangle and the sheet shows an amber box titled Needs attention with the reason.
| Reason | Meaning |
|---|---|
| An order filled more than was sent | A child order filled past its own size. |
| Filled more than the order's size | The order filled past its size. |
| Order value can't be tracked | Aura can't follow the order's filled value. |
| Algo not supported here | Aura can't run the order's algo right now, so it holds the order without trading it. |
| Hedge leg can't be traded | A spreader's hedge leg was rejected or cancelled by the exchange. |
| API key refused | The exchange refused the account's API key while the order was open. |
| Exchange ignored reduce-only | The exchange reported a reduce-only child order as not reduce-only. |
For every reason except Algo not supported here and API key refused, Aura also cancels the order. API key refused clears once the account connects again with a working key. To update the key, see Connection status.