Orders and Execution

Targeted answers for orders that fail, fill weirdly, or behave unexpectedly across the three trade rails.

---

My order failed. Pre-trade checks block obvious failures; if it still failed, the reason is in the Activity log. Run through:

• Balance — confirm the wallet / broker account has enough of the right asset to settle, plus gas (for on-chain) or buying power (for broker).
• Slippage tolerance — a tight slippage on a volatile pair will refuse fills. Increase tolerance or wait.
• Venue status — broker market hours (stocks), Hyperliquid status (perps), Polymarket order-book depth (predictions). Off-hours or thin books cause rejection.
• Activity log — open the failed order's detail and read the venue's exact error (e.g. "insufficient margin", "price moved", "market closed").

Most failures are recoverable: address the cause and re-submit. Alphio does not silently route to a different venue or asset.

Order shows executed but no position. Almost always a view-filter mismatch, not a missing position:

• Wallet selector in Activity log — you may be viewing a different bound wallet.
• Chain filter — perps live on Hyperliquid, spot on Ethereum, predictions on Polygon.
• Asset / date filters — clear them; old default filters can hide today's fill.

If the Activity log row shows the fill but no position appears anywhere after a hard refresh, contact support with the order ID.

How does Alphio retry failed orders? Alphio uses a layered retry that's designed to be predictable, not aggressive:

• Pre-trade validation — balance, gas, slippage are checked before the order is sent.
• Transient-error retry — RPC timeouts, broker API blips, and similar are retried with backoff.
• Gas / slippage bump — for on-chain orders, gas is increased on congestion within a safe ceiling.
• Hard stop — once all retries fail, the final error is written to the Activity log and no further attempts are made.

Alphio never re-routes to a different venue or asset to "force" a fill.

What is slippage and how do I control it? Slippage is the price difference between when you submit and when you fill. You set the maximum slippage tolerance before confirming an order:

• Tight tolerance (e.g. 0.1%) — protects price but refuses fills on volatile pairs.
• Loose tolerance (e.g. 1–3%) — more fills, but worse average price on fast-moving markets.

The Trade Modal shows the current bid / ask spread and a recommended tolerance. For thin pairs (low liquidity, low-cap tokens), expect higher slippage requirements; for blue-chip pairs, very tight tolerances are fine.

Order partially filled — what happens next? Behavior depends on the order type:

• Market orders — the unfilled remainder is cancelled; the venue couldn't match it at acceptable prices.
• Limit orders — the unfilled remainder stays open at your limit price until filled, cancelled, or expired.

Check the order's row in Activity log — the filled qty, remaining qty, and current status are all on the row. To replace the remainder at a different price, cancel the open remainder and submit a new order.

Trading fees — see Reference. Effective trading fees are the sum of the venue fee and an Alphio service fee, and they vary by tier and rail.

warning

Full fee schedule lands at /trade/trading-fees in Phase 2. Until then, the Trade Modal shows the total fee for the specific trade before you confirm — that is the authoritative number for that order.