Troubleshooting#
Common issues by symptom, then a reference for the error codes an order can end with. For what each order status means, see Managing Orders.
Common issues#
API key rejected when linking an exchange#
Key validation runs right after you save the key, and the venue's error message is shown inline. The usual causes:
- IP allowlist not applied yet. Most venues require you to allowlist Anboto's IP addresses on the API key. Copy the account-specific IPs from Settings → Linked Exchanges and add them on the exchange side, then save the key again.
- Missing trade permission. The key must have trading enabled (spot and/or futures, depending on what you trade).
- WOO X: the key needs "Trade Spot & Futures" enabled explicitly.
See Connect Exchanges for per-venue walkthroughs.
Order rejected at submission#
Submission runs validation before the order is accepted. Rejections at this stage are configuration problems:
- Quantity too small — below the venue's minimum order size, or not a multiple of the contract size.
- Duration missing — TWAP, VWAP, POV, and Implementation Shortfall all require a duration (Scale does not).
- Duration out of range — must be between 60 seconds and 30 days.
- Start time too far out — the start time must be within one day.
- End time in the past — the end time must be in the future.
- Invalid symbol or exchange — the symbol isn't tradable on the selected account.
"Futures disabled on this account"#
The venue account behind your API key doesn't have futures trading enabled. Enable futures on the exchange, then re-link the key.
Insufficient funds#
The order needs the full notional available on the venue account (a small buffer is applied on top). Free up or deposit funds on the exchange, then resubmit.
Order shows Paused#
If the venue rate-limits the account, the algo pauses briefly — typically around 2 minutes — and resumes automatically. No action is needed, and there is nothing to resume manually: pausing is triggered by the platform, not by you. See order statuses.
Order stopped with "Exchange restricted further placement"#
The venue blocked the account from placing further orders — usually a compliance or account-level restriction. The order is cancelled and not retried. Contact the exchange to resolve the restriction.
A Metrics page 404s on a direct URL#
pro.anboto.xyz/metrics/post-trade-analysis and pro.anboto.xyz/metrics/trading-stats currently return a 404 when opened directly, pasted, or bookmarked. Reach them through the Metrics menu inside the app instead. A fix is in progress.
A saved order will not start#
Starting a saved order requires an active subscription. Check the Billing page, then start the order again.
Error code reference#
When a parent order stops with an error, the code below appears in the order's status/message. API users receive the same codes in UPPER_SNAKE form — see the Anboto Trading API docs.
| Code | Meaning | What to do |
|---|---|---|
other |
Unclassified error | Retry; if it recurs, contact support |
quantity_exceed |
Shown as "unexpected issue" | Contact support |
authentication_error |
The venue rejected the account's credentials | Check the API key and IP allowlist under Settings → Linked Exchanges, then re-link if needed |
insufficient_funds |
Not enough balance on the venue account for the order's notional | Fund the account or reduce the quantity, then resubmit |
rate_limit_exceeded |
The venue rate-limited the account | Nothing — the order auto-pauses and resumes |
ddos_protection |
The venue's DDoS protection throttled requests | Wait and resubmit; if persistent, contact support |
exchange_not_available |
The venue was unreachable or in maintenance | Wait for the venue to recover, then resubmit |
network_error |
Connectivity problem reaching the venue | Resubmit; if persistent, contact support |
invalid_order |
Too many child orders were rejected by the venue — the venue's rejection reason is attached to the order | Read the attached reason and fix the order parameters or account state it points to |
exchange_error |
Generic venue-side error | Read the attached message; resubmit or contact the exchange |
ems_instances_down |
Platform-side issue | Contact support |
slippage_exceeded |
Execution stopped after exceeding the slippage tolerance | Review the limit/tolerance settings and resubmit for the remainder |
expiry_reached |
The order reached its expiry before completing | Place a new order for the remainder; see Expiry |
parent_order_was_terminated |
The order was terminated before completion | Place a new order for the remainder if needed |
insufficient_liquidity |
There was not enough liquidity on the book to execute the order at acceptable prices | Reduce the order size, relax the limit price, or spread the order over a longer duration |
trading_restricted |
The venue restricted trading on the account (terminal — not retried) | Contact the exchange |
Two legacy codes from DeFi execution — max_fee_per_gas_is_too_low and max_priority_fee_per_gas_is_too_low — may still appear on historical orders and can be ignored for exchange trading.
Still stuck?#
Contact Customer Support from the top-right corner of pro.anboto.xyz, which opens a Telegram conversation with the team. Include the order ID and the error message shown on the order.