Skip to content

Managing Orders#

This page covers the lifecycle of a parent order after you submit it — the tabs where orders live, the statuses you'll see, and the actions available at each stage. For reading the order table itself (columns, fill-progress bar, export), see Order Monitoring & History.

Order tabs#

The orders panel is organized into tabs:

Tab Contents
Regular orders Live algo parent orders
Trigger orders Orders waiting on a trigger condition
Multi Legs Pair / multi-leg orders
Portfolio Positions and balances on your connected accounts
History Filled, finished, cancelled, stopped, rejected, and timed-out orders

Orders you saved instead of submitting are listed with your saved orders — see Saved orders below.

Order statuses#

A parent order moves through a small set of statuses, shown in the Status column. When a status comes with an explanation, an ⓘ icon sits next to it: hover it to read the reason.

While the order is live

Status Meaning
Pending Accepted and queued to start
Running Actively executing — the progress bar shows filled vs. resting vs. remaining quantity
Partly Filled Part of the quantity has executed and the order is still working
Pacing Anboto is slowing the order to stay within venue limits. It is still active, and no action is needed
Paused — exchange rate limit The exchange hit an IP rate limit on this connection. Trading resumes automatically; you don't need to cancel
Pausing / Paused The platform has temporarily paused the order. Execution resumes automatically; you cannot pause or resume an order yourself
Canceling A cancel request is in flight

Once the order has ended

Status Meaning
Filled The full target quantity executed
Finished The order ended with at least 99% of its quantity filled; the tiny remainder stays unfilled. A Passive order that reaches its time limit also shows Finished, with "time limit" in the ⓘ tooltip
Time limit reached The order reached the end of its time window — its duration plus the extend-duration grace window, or its expiry — before it was filled. Error code expiry_reached
Cancelled by user You cancelled the order. Fills already executed stand
Cancelled The order was cancelled before completion without a more specific status; any fills already executed stand
Stopped The order stopped for a named reason — for example not enough balance or margin, a position limit on the exchange, or an exchange restriction. The reason is in the ⓘ tooltip
Rejected The order could not run — see Troubleshooting for common reasons

Every row expands to a full parameter read-out — trading style, urgency, would/limit prices, clip size, placement, POV participation, and the rest — so you can always see exactly what an order was configured to do.

Cancelling an order#

Cancel is the only action on a live parent order: there is no amend, and pausing is something the platform does automatically at venue rate limits, not something you trigger. Cancel is available on any live order unless it is already cancelled, fully filled, or a cancel is already in flight.

Cancelling:

  • stops the algo from placing new child orders,
  • cancels child orders currently resting on the book,
  • leaves fills already executed in place — they are not reversed.

The order shows Canceling while the resting quantity is pulled, then Cancelled by user.

Changing a live order#

There is no amend on a live order. To change any parameter — duration, limit price, trading style, quantity, POV participation — cancel the order and place a new one for the remaining quantity. The expanded row shows the executed quantity so far, which makes the remainder easy to compute.

Saved orders#

The order review dialog offers Save for Later instead of submitting immediately. A saved order is not working in the market — it sits in your saved-orders list until you start it, and offers two actions:

  • Start — submits the order as configured. It requires an active subscription; see Billing.
  • Delete — removes the saved order.

Expiry#

Every order carries an expiry setting (default: 30 days). The 1 month option in Advanced Settings is exactly 30 days (720 hours) — the same value the public API uses — so the GUI and the API behave the same on expiry. An order with a duration also has a scheduled end: extend duration (on by default) gives the algo a short grace window past that end to finish the tail — see Advanced settings for the exact window.

An order still working when it reaches the end of that window, or its expiry, stops with the status Time limit reached and the error code expiry_reached — see the error code reference. Place a new order for the remaining quantity. If at least 99% was already filled, the order shows Finished instead.

Notifications#

Order lifecycle events — submitted, filled, cancelled, rejected — and trigger events — created, enabled, disabled, fired — also fire through the notification center when the matching channel is on. By default every channel is off; turn on the ones you want from Settings → Notifications.

Multi-leg orders#

Completed multi-leg (pair) orders in the History tab offer a Reverse action, which pre-fills a new order for the opposite trade — useful for unwinding a pair position.

Order details page#

Order rows in the orders panel — Regular orders, History and the other order tabs — and in Transaction History end with a View order details arrow (›). It opens the order's own page, with its fill charts, benchmark lines and fills table, at a link you can share. See The order page, and Post-Trade Analysis for the aggregated metrics.